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 head, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW:
20 FreeBSD 11.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 If a Makefile in a tests/ directory was auto-generating a Kyuafile
36 instead of providing an explicit one, this would prevent such
37 Makefile from providing its own Kyuafile in the future during
38 NO_CLEAN builds. This has been fixed in the Makefiles but manual
39 intervention is needed to clean an objdir if you use NO_CLEAN:
40 # find /usr/obj -name Kyuafile | xargs rm -f
43 The behavior of gss_pseudo_random() for the krb5 mechanism
44 has changed, for applications requesting a longer random string
45 than produced by the underlying enctype's pseudo-random() function.
46 In particular, the random string produced from a session key of
47 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
48 be different at the 17th octet and later, after this change.
49 The counter used in the PRF+ construction is now encoded as a
50 big-endian integer in accordance with RFC 4402.
51 __FreeBSD_version is bumped to 1100004.
54 The WITHOUT_ATF build knob has been removed and its functionality
55 has been subsumed into the more generic WITHOUT_TESTS. If you were
56 using the former to disable the build of the ATF libraries, you
57 should change your settings to use the latter.
60 The default version of mtree is nmtree which is obtained from
61 NetBSD. The output is generally the same, but may vary
62 slightly. If you found you need identical output adding
63 "-F freebsd9" to the command line should do the trick. For the
64 time being, the old mtree is available as fmtree.
67 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
68 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
69 1.1.4_8 and verify bsdyml not linked in, before running "make
71 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
73 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
76 The rc.d/jail script has been updated to support jail(8)
77 configuration file. The "jail_<jname>_*" rc.conf(5) variables
78 for per-jail configuration are automatically converted to
79 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
80 This is transparently backward compatible. See below about some
81 incompatibilities and rc.conf(5) manual page for more details.
83 These variables are now deprecated in favor of jail(8) configuration
84 file. One can use "rc.d/jail config <jname>" command to generate
85 a jail(8) configuration file in /var/run/jail.<jname>.conf without
86 running the jail(8) utility. The default pathname of the
87 configuration file is /etc/jail.conf and can be specified by
88 using $jail_conf or $jail_<jname>_conf variables.
90 Please note that jail_devfs_ruleset accepts an integer at
91 this moment. Please consider to rewrite the ruleset name
95 BIND has been removed from the base system. If all you need
96 is a local resolver, simply enable and start the local_unbound
97 service instead. Otherwise, several versions of BIND are
98 available in the ports tree. The dns/bind99 port is one example.
100 With this change, nslookup(1) and dig(1) are no longer in the base
101 system. Users should instead use host(1) and drill(1) which are
102 in the base system. Alternatively, nslookup and dig can
103 be obtained by installing the dns/bind-tools port.
106 With the addition of unbound(8), a new unbound user is now
107 required during installworld. "mergemaster -p" can be used to
108 add the user prior to installworld, as documented in the handbook.
111 OpenSSH is now built with DNSSEC support, and will by default
112 silently trust signed SSHFP records. This can be controlled with
113 the VerifyHostKeyDNS client configuration setting. DNSSEC support
114 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
117 The GNU Compiler Collection and C++ standard library (libstdc++)
118 are no longer built by default on platforms where clang is the system
119 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
123 The PROCDESC kernel option is now part of the GENERIC kernel
124 configuration and is required for the rwhod(8) to work.
125 If you are using custom kernel configuration, you should include
129 The API and ABI related to the Capsicum framework was modified
130 in backward incompatible way. The userland libraries and programs
131 have to be recompiled to work with the new kernel. This includes the
132 following libraries and programs, but the whole buildworld is
133 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
134 kdump, procstat, rwho, rwhod, uniq.
137 AES-NI intrinsic support has been added to gcc. The AES-NI module
138 has been updated to use this support. A new gcc is required to build
139 the aesni module on both i386 and amd64.
142 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
143 Thus "device padlock_rng" and "device rdrand_rng" should be
144 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
147 WITH_ICONV has been split into two feature sets. WITH_ICONV now
148 enables just the iconv* functionality and is now on by default.
149 WITH_LIBICONV_COMPAT enables the libiconv api and link time
150 compatability. Set WITHOUT_ICONV to build the old way.
151 If you have been using WITH_ICONV before, you will very likely
152 need to turn on WITH_LIBICONV_COMPAT.
155 INVARIANTS option now enables DEBUG for code with OpenSolaris and
156 Illumos origin, including ZFS. If you have INVARIANTS in your
157 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
159 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
160 locks if WITNESS option was set. Because that generated a lot of
161 witness(9) reports and all of them were believed to be false
162 positives, this is no longer done. New option OPENSOLARIS_WITNESS
163 can be used to achieve the previous behavior.
166 Timer values in IPv6 data structures now use time_uptime instead
167 of time_second. Although this is not a user-visible functional
168 change, userland utilities which directly use them---ndp(8),
169 rtadvd(8), and rtsold(8) in the base system---need to be updated
173 find -delete can now delete the pathnames given as arguments,
174 instead of only files found below them or if the pathname did
175 not contain any slashes. Formerly, the following error message
178 find: -delete: <path>: relative path potentially not safe
180 Deleting the pathnames given as arguments can be prevented
181 without error messages using -mindepth 1 or by changing
182 directory and passing "." as argument to find. This works in the
183 old as well as the new version of find.
186 Behavior of devfs rules path matching has been changed.
187 Pattern is now always matched against fully qualified devfs
188 path and slash characters must be explicitly matched by
189 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
190 subdirectories must be reviewed.
193 The default ARM ABI has changed to the ARM EABI. The old ABI is
194 incompatible with the ARM EABI and all programs and modules will
195 need to be rebuilt to work with a new kernel.
197 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
199 NOTE: Support for the old ABI will be removed in the future and
200 users are advised to upgrade.
203 pkg_install has been disconnected from the build if you really need it
204 you should add WITH_PKGTOOLS in your src.conf(5).
207 Most of network statistics structures were changed to be able
208 keep 64-bits counters. Thus all tools, that work with networking
209 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
212 Fix targets that run multiple make's to use && rather than ;
213 so that subsequent steps depend on success of previous.
215 NOTE: if building 'universe' with -j* on stable/8 or stable/9
216 it would be better to start the build using bmake, to avoid
217 overloading the machine.
220 Fix a bug that allowed a tracing process (e.g. gdb) to write
221 to a memory-mapped file in the traced process's address space
222 even if neither the traced process nor the tracing process had
223 write access to that file.
226 CVS has been removed from the base system. An exact copy
227 of the code is available from the devel/cvs port.
230 Some people report the following error after the switch to bmake:
232 make: illegal option -- J
233 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
235 *** [buildworld] Error code 2
237 this likely due to an old instance of make in
238 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
239 which src/Makefile will use that blindly, if it exists, so if
240 you see the above error:
242 rm -rf `make -V MAKEPATH`
247 Use bmake by default.
248 Whereas before one could choose to build with bmake via
249 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
250 make. The goal is to remove these knobs for 10-RELEASE.
252 It is worth noting that bmake (like gmake) treats the command
253 line as the unit of failure, rather than statements within the
254 command line. Thus '(cd some/where && dosomething)' is safer
255 than 'cd some/where; dosomething'. The '()' allows consistent
256 behavior in parallel build.
259 Fix a bug that allows NFS clients to issue READDIR on files.
262 The WITHOUT_IDEA option has been removed because
263 the IDEA patent expired.
266 The sysctl which controls TRIM support under ZFS has been renamed
267 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
271 The mergemaster command now uses the default MAKEOBJDIRPREFIX
272 rather than creating it's own in the temporary directory in
273 order allow access to bootstrapped versions of tools such as
274 install and mtree. When upgrading from version of FreeBSD where
275 the install command does not support -l, you will need to
276 install a new mergemaster command if mergemaster -p is required.
277 This can be accomplished with the command (cd src/usr.sbin/mergemaster
281 Legacy ATA stack, disabled and replaced by new CAM-based one since
282 FreeBSD 9.0, completely removed from the sources. Kernel modules
283 atadisk and atapi*, user-level tools atacontrol and burncd are
284 removed. Kernel option `options ATA_CAM` is now permanently enabled
288 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
289 and socketpair(2). Software, in particular Kerberos, may
290 automatically detect and use these during building. The resulting
291 binaries will not work on older kernels.
294 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
295 information, see the respective 20130304 entry).
298 Recent commits to callout(9) changed the size of struct callout,
299 so the KBI is probably heavily disturbed. Also, some functions
300 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
301 by macros. Every kernel module using it won't load, so rebuild
304 The ctl device has been re-enabled in GENERIC for i386 and amd64,
305 but does not initialize by default (because of the new CTL_DISABLE
306 option) to save memory. To re-enable it, remove the CTL_DISABLE
307 option from the kernel config file or set kern.cam.ctl.disable=0
308 in /boot/loader.conf.
311 The ctl device has been disabled in GENERIC for i386 and amd64.
312 This was done due to the extra memory being allocated at system
313 initialisation time by the ctl driver which was only used if
314 a CAM target device was created. This makes a FreeBSD system
315 unusable on 128MB or less of RAM.
318 A new compression method (lz4) has been merged to -HEAD. Please
319 refer to zpool-features(7) for more information.
321 Please refer to the "ZFS notes" section of this file for information
322 on upgrading boot ZFS pools.
325 A BSD-licensed patch(1) variant has been added and is installed
326 as bsdpatch, being the GNU version the default patch.
327 To inverse the logic and use the BSD-licensed one as default,
328 while having the GNU version installed as gnupatch, rebuild
329 and install world with the WITH_BSD_PATCH knob set.
332 Due to the use of the new -l option to install(1) during build
333 and install, you must take care not to directly set the INSTALL
334 make variable in your /etc/make.conf, /etc/src.conf, or on the
335 command line. If you wish to use the -C flag for all installs
336 you may be able to add INSTALL+=-C to /etc/make.conf or
340 The install(1) option -M has changed meaning and now takes an
341 argument that is a file or path to append logs to. In the
342 unlikely event that -M was the last option on the command line
343 and the command line contained at least two files and a target
344 directory the first file will have logs appended to it. The -M
345 option served little practical purpose in the last decade so its
346 use is expected to be extremely rare.
349 After switching to Clang as the default compiler some users of ZFS
350 on i386 systems started to experience stack overflow kernel panics.
351 Please consider using 'options KSTACK_PAGES=4' in such configurations.
354 GEOM_LABEL now mangles label names read from file system metadata.
355 Mangling affect labels containing spaces, non-printable characters,
356 '%' or '"'. Device names in /etc/fstab and other places may need to
360 By default, only the 10 most recent kernel dumps will be saved. To
361 restore the previous behaviour (no limit on the number of kernel dumps
362 stored in the dump directory) add the following line to /etc/rc.conf:
367 With the addition of auditdistd(8), a new auditdistd user is now
368 required during installworld. "mergemaster -p" can be used to
369 add the user prior to installworld, as documented in the handbook.
372 The sin6_scope_id member variable in struct sockaddr_in6 is now
373 filled by the kernel before passing the structure to the userland via
374 sysctl or routing socket. This means the KAME-specific embedded scope
375 id in sin6_addr.s6_addr[2] is always cleared in userland application.
376 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
377 __FreeBSD_version is bumped to 1000025.
380 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
381 This means that the world and kernel will be compiled with clang
382 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
383 and /usr/bin/cpp. To disable this behavior and revert to building
384 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
385 of current may need to bootstrap WITHOUT_CLANG first if the clang
386 build fails (its compatibility window doesn't extend to the 9 stable
390 The IPFIREWALL_FORWARD kernel option has been removed. Its
391 functionality now turned on by default.
394 The ZERO_COPY_SOCKET kernel option has been removed and
395 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
396 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
397 mechanism which is not safe and may result in kernel crashes.
398 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
399 driver supports disposeable external page sized mbuf storage.
400 Proper replacements for both zero-copy mechanisms are under
401 consideration and will eventually lead to complete removal
402 of the two kernel options.
405 The IPv4 network stack has been converted to network byte
406 order. The following modules need to be recompiled together
407 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
408 pf(4), ipfw(4), ng_ipfw(4), stf(4).
411 Support for non-MPSAFE filesystems was removed from VFS. The
412 VFS_VERSION was bumped, all filesystem modules shall be
416 All the non-MPSAFE filesystems have been disconnected from
417 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
418 portalfs, smbfs, xfs.
421 The interface cloning API and ABI has changed. The following
422 modules need to be recompiled together with kernel:
423 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
424 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
425 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
428 The sdhci driver was split in two parts: sdhci (generic SD Host
429 Controller logic) and sdhci_pci (actual hardware driver).
430 No kernel config modifications are required, but if you
431 load sdhc as a module you must switch to sdhci_pci instead.
434 Import the FUSE kernel and userland support into base system.
437 The GNU sort(1) program has been removed since the BSD-licensed
438 sort(1) has been the default for quite some time and no serious
439 problems have been reported. The corresponding WITH_GNU_SORT
443 The pfil(9) API/ABI for AF_INET family has been changed. Packet
444 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
448 The net80211(4) ABI has been changed to allow for improved driver
449 PS-POLL and power-save support. All wireless drivers need to be
450 recompiled to work with the new kernel.
453 The random(4) support for the VIA hardware random number
454 generator (`PADLOCK') is no longer enabled unconditionally.
455 Add the padlock_rng device in the custom kernel config if
456 needed. The GENERIC kernels on i386 and amd64 do include the
457 device, so the change only affects the custom kernel
461 The pf(4) packet filter ABI has been changed. pfctl(8) and
462 snmp_pf module need to be recompiled to work with new kernel.
465 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
466 to -HEAD. Pools that have empty_bpobj in active state can not be
467 imported read-write with ZFS implementations that do not support
468 this feature. For more information read the zpool-features(5)
472 The sparc64 ZFS loader has been changed to no longer try to auto-
473 detect ZFS providers based on diskN aliases but now requires these
474 to be explicitly listed in the OFW boot-device environment variable.
477 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
478 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
479 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
482 The following sysctls and tunables have been renamed for consistency
483 with other variables:
484 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
485 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
488 The sort utility has been replaced with BSD sort. For now, GNU sort
489 is also available as "gnusort" or the default can be set back to
490 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
491 installed as "bsdsort".
494 A new version of ZFS (pool version 5000) has been merged to -HEAD.
495 Starting with this version the old system of ZFS pool versioning
496 is superseded by "feature flags". This concept enables forward
497 compatibility against certain future changes in functionality of ZFS
498 pools. The first read-only compatible "feature flag" for ZFS pools
499 is named "com.delphix:async_destroy". For more information
500 read the new zpool-features(5) manual page.
501 Please refer to the "ZFS notes" section of this file for information
502 on upgrading boot ZFS pools.
505 The malloc(3) implementation embedded in libc now uses sources imported
506 as contrib/jemalloc. The most disruptive API change is to
507 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
508 delete it prior to installworld, and optionally re-create it using the
509 new format after rebooting. See malloc.conf(5) for details
510 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
514 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
515 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
516 now spelled mips. This is to aid compatibility with third-party
517 software that expects this naming scheme in uname(3). Little-endian
518 settings are unchanged. If you are updating a big-endian mips64 machine
519 from before this change, you may need to set MACHINE_ARCH=mips64 in
520 your environment before the new build system will recognize your machine.
523 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
527 Now unix domain sockets behave "as expected" on nullfs(5). Previously
528 nullfs(5) did not pass through all behaviours to the underlying layer,
529 as a result if we bound to a socket on the lower layer we could connect
530 only to the lower path; if we bound to the upper layer we could connect
531 only to the upper path. The new behavior is one can connect to both the
532 lower and the upper paths regardless what layer path one binds to.
535 The getifaddrs upgrade path broken with 20111215 has been restored.
536 If you have upgraded in between 20111215 and 20120209 you need to
537 recompile libc again with your kernel. You still need to recompile
538 world to be able to configure CARP but this restriction already
542 The set_rcvar() function has been removed from /etc/rc.subr. All
543 base and ports rc.d scripts have been updated, so if you have a
544 port installed with a script in /usr/local/etc/rc.d you can either
545 hand-edit the rcvar= line, or reinstall the port.
547 An easy way to handle the mass-update of /etc/rc.d:
548 rm /etc/rc.d/* && mergemaster -i
551 panic(9) now stops other CPUs in the SMP systems, disables interrupts
552 on the current CPU and prevents other threads from running.
553 This behavior can be reverted using the kern.stop_scheduler_on_panic
555 The new behavior can be incompatible with kern.sync_on_panic.
558 The carp(4) facility has been changed significantly. Configuration
559 of the CARP protocol via ifconfig(8) has changed, as well as format
560 of CARP events submitted to devd(8) has changed. See manual pages
561 for more information. The arpbalance feature of carp(4) is currently
562 not supported anymore.
564 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
565 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
566 need to be recompiled.
569 The acpi_wmi(4) status device /dev/wmistat has been renamed to
573 The option VFS_ALLOW_NONMPSAFE option has been added in order to
574 explicitely support non-MPSAFE filesystems.
575 It is on by default for all supported platform at this present
579 The broken amd(4) driver has been replaced with esp(4) in the amd64,
580 i386 and pc98 GENERIC kernel configuration files.
583 sysinstall has been removed
586 The stable/9 branch created in subversion. This corresponds to the
587 RELENG_9 branch in CVS.
590 This commit modifies vfs_register() so that it uses a hash
591 calculation to set vfc_typenum, which is enabled by default.
592 The first time a system is booted after this change, the
593 vfc_typenum values will change for all file systems. The
594 main effect of this is a change to the NFS server file handles
595 for file systems that use vfc_typenum in their fsid, such as ZFS.
596 It will, however, prevent vfc_typenum from changing when file
597 systems are loaded in a different order for subsequent reboots.
598 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
599 until you are ready to remount all NFS clients after a reboot.
602 Bump the shared library version numbers for libraries that
603 do not use symbol versioning, have changed the ABI compared
604 to stable/8 and which shared library version was not bumped.
605 Done as part of 9.0-RELEASE cycle.
608 During the merge of Capsicum features, the fget(9) KPI was modified.
609 This may require the rebuilding of out-of-tree device drivers --
610 issues have been reported specifically with the nVidia device driver.
611 __FreeBSD_version is bumped to 900041.
613 Also, there is a period between 20110811 and 20110814 where the
614 special devices /dev/{stdin,stdout,stderr} did not work correctly.
615 Building world from a kernel during that window may not work.
618 The packet filter (pf) code has been updated to OpenBSD 4.5.
619 You need to update userland tools to be in sync with kernel.
620 This update breaks backward compatibility with earlier pfsync(4)
621 versions. Care must be taken when updating redundant firewall setups.
624 The following sysctls and tunables are retired on x86 platforms:
626 machdep.hlt_logical_cpus
627 The following sysctl is retired:
628 machdep.hyperthreading_allowed
629 The sysctls were supposed to provide a way to dynamically offline and
630 online selected CPUs on x86 platforms, but the implementation has not
631 been reliable especially with SCHED_ULE scheduler.
632 machdep.hyperthreading_allowed tunable is still available to ignore
633 hyperthreading CPUs at OS level.
634 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
635 where X is an APIC ID of a CPU. Be advised, though, that disabling
636 CPUs in non-uniform fashion will result in non-uniform topology and
637 may lead to sub-optimal system performance with SCHED_ULE, which is
641 cpumask_t type is retired and cpuset_t is used in order to describe
645 Changes to ifconfig(8) for dynamic address family detection mandate
646 that you are running a kernel of 20110525 or later. Make sure to
647 follow the update procedure to boot a new kernel before installing
651 Support for sun4v architecture is officially dropped
654 Several KPI breaking changes have been committed to the mii(4) layer,
655 the PHY drivers and consequently some Ethernet drivers using mii(4).
656 This means that miibus.ko and the modules of the affected Ethernet
657 drivers need to be recompiled.
659 Note to kernel developers: Given that the OUI bit reversion problem
660 was fixed as part of these changes all mii(4) commits related to OUIs,
661 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
662 handling, no longer can be merged verbatim to stable/8 and previous
666 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
667 into their kernel configurations along with 'device pci'.
670 The default NFS client is now the new NFS client, so fstype "newnfs"
671 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
672 Although mounts via fstype "nfs" will usually work without userland
673 changes, it is recommended that the mount(8) and mount_nfs(8)
674 commands be rebuilt from sources and that a link to mount_nfs called
675 mount_oldnfs be created. The new client is compiled into the
676 kernel with "options NFSCL" and this is needed for diskless root
677 file systems. The GENERIC kernel configs have been changed to use
678 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
679 To use the regular/old client, you can "mount -t oldnfs ...". For
680 a diskless root file system, you must also include a line like:
682 vfs.root.mountfrom="oldnfs:"
684 in the boot/loader.conf on the root fs on the NFS server to make
685 a diskless root fs use the old client.
688 The GENERIC kernels for all architectures now default to the new
689 CAM-based ATA stack. It means that all legacy ATA drivers were
690 removed and replaced by respective CAM drivers. If you are using
691 ATA device names in /etc/fstab or other places, make sure to update
692 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
693 where 'Y's are the sequential numbers starting from zero for each type
694 in order of detection, unless configured otherwise with tunables,
695 see cam(4)). There will be symbolic links created in /dev/ to map
696 old adX devices to the respective adaY. They should provide basic
697 compatibility for file systems mounting in most cases, but they do
698 not support old user-level APIs and do not have respective providers
699 in GEOM. Consider using updated management tools with new device names.
701 It is possible to load devices ahci, ata, siis and mvs as modules,
702 but option ATA_CAM should remain in kernel configuration to make ata
703 module work as CAM driver supporting legacy ATA controllers. Device ata
704 still can be used in modular fashion (atacore + ...). Modules atadisk
705 and atapi* are not used and won't affect operation in ATA_CAM mode.
706 Note that to use CAM-based ATA kernel should include CAM devices
707 scbus, pass, da (or explicitly ada), cd and optionally others. All of
708 them are parts of the cam module.
710 ataraid(4) functionality is now supported by the RAID GEOM class.
711 To use it you can load geom_raid kernel module and use graid(8) tool
712 for management. Instead of /dev/arX device names, use /dev/raid/rX.
714 No kernel config options or code have been removed, so if a problem
715 arises, please report it and optionally revert to the old ATA stack.
716 In order to do it you can remove from the kernel config:
721 , and instead add back:
722 device atadisk # ATA disk drives
723 device ataraid # ATA RAID drives
724 device atapicd # ATAPI CDROM drives
725 device atapifd # ATAPI floppy drives
726 device atapist # ATAPI tape drives
729 The default NFS server has been changed to the new server, which
730 was referred to as the experimental server. If you need to switch
731 back to the old NFS server, you must now put the "-o" option on
732 both the mountd and nfsd commands. This can be done using the
733 mountd_flags and nfs_server_flags rc.conf variables until an
734 update to the rc scripts is committed, which is coming soon.
737 The GNU Objective-C runtime library (libobjc), and other Objective-C
738 related components have been removed from the base system. If you
739 require an Objective-C library, please use one of the available ports.
742 ath(4) has been split into bus- and device- modules. if_ath contains
743 the HAL, the TX rate control and the network device code. if_ath_pci
744 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
745 contains the AHB glue. Users need to load both if_ath_pci and if_ath
746 in order to use ath on everything else.
748 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
749 need to load if_ath and if_ath_pci for ath(4) operation.
752 As part of the replacement of sysinstall, the process of building
753 release media has changed significantly. For details, please re-read
754 release(7), which has been updated to reflect the new build process.
757 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
758 is the last available version under GPLv2. It brings a number of new
759 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
760 4.1 and SSE 4.2), better support for powerpc64, a number of new
761 directives, and lots of other small improvements. See the ChangeLog
762 file in contrib/binutils for the full details.
765 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
766 compliant, and will now use half of hash for authentication.
767 This will break interoperability with all stacks (including all
768 actual FreeBSD versions) who implement
769 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
771 The only workaround with such peers is to use another HMAC
772 algorithm for IPsec ("phase 2") authentication.
775 Remove the uio_yield prototype and symbol. This function has
776 been misnamed since it was introduced and should not be
777 globally exposed with this name. The equivalent functionality
778 is now available using kern_yield(curthread->td_user_pri).
779 The function remains undocumented.
782 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
783 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
784 for scalar sysctls is defined but disabled. Code that needs
785 UQUAD to pass the type checking that must compile on older
786 systems where the define is not present can check against
787 __FreeBSD_version >= 900030.
789 The system dialog(1) has been replaced with a new version previously
790 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
791 with the previous version, but the libdialog associated with it has
792 a largely incompatible API. As such, the original version of libdialog
793 will be kept temporarily as libodialog, until its base system consumers
794 are replaced or updated. Bump __FreeBSD_version to 900030.
797 If you are trying to run make universe on a -stable system, and you get
798 the following warning:
799 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
800 unknown. config(8) likely too old."
801 or something similar to it, then you must upgrade your -stable system
802 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
803 stable/8) or build the config from the latest stable/8 branch and
804 install it on your system.
806 Prior to this date, building a current universe on 8-stable system from
807 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
808 error in the first kernel build phase. A new config on those old
809 systems will fix that problem for older versions of -current.
812 The TCP stack has been modified to allow Khelp modules to interact with
813 it via helper hook points and store per-connection data in the TCP
814 control block. Bump __FreeBSD_version to 900029. User space tools that
815 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
819 Generic IEEE 802.3 annex 31B full duplex flow control support has been
820 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
821 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
822 to take advantage of it instead of using custom implementations. This
823 means that these drivers now no longer unconditionally advertise
824 support for flow control but only do so if flow control is a selected
825 media option. This was implemented in the generic support that way in
826 order to allow flow control to be switched on and off via ifconfig(8)
827 with the PHY specific default to typically off in order to protect
828 from unwanted effects. Consequently, if you used flow control with
829 one of the above mentioned drivers you now need to explicitly enable
831 ifconfig bge0 media auto mediaopt flowcontrol
833 Along with the above mentioned changes generic support for setting
834 1000baseT master mode also has been added and brgphy(4), ciphy(4),
835 e1000phy(4) as well as ip1000phy(4) have been converted to take
836 advantage of it. This means that these drivers now no longer take the
837 link0 parameter for selecting master mode but the master media option
838 has to be used instead, for example like in the following:
839 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
841 Selection of master mode now is also available with all other PHY
842 drivers supporting 1000baseT.
845 The TCP stack has received a significant update to add support for
846 modularised congestion control and generally improve the clarity of
847 congestion control decisions. Bump __FreeBSD_version to 900025. User
848 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
849 sockstat) need to be recompiled.
852 The man(1) utility has been replaced by a new version that no longer
853 uses /etc/manpath.config. Please consult man.conf(5) for how to
854 migrate local entries to the new format.
857 The copyright strings printed by login(1) and sshd(8) at the time of a
858 new connection have been removed to follow other operating systems and
862 A workaround for a fixed ld bug has been removed in kernel code,
863 so make sure that your system ld is built from sources after
864 revision 210245 from 2010-07-19 (r211583 if building head kernel
865 on stable/8, r211584 for stable/7; both from 2010-08-21).
866 A symptom of incorrect ld version is different addresses for
867 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
870 The $ipv6_prefer variable in rc.conf(5) has been split into
871 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
873 The $ip6addrctl_policy is a variable to choose a pre-defined
874 address selection policy set by ip6addrctl(8). A value
875 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
878 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
879 flag (see an entry of 20090926) is set on an interface with no
880 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
881 security reason. If you want IPv6 link-local address on all
882 interfaces by default, set this to "YES".
884 The old ipv6_prefer="YES" is equivalent to
885 ipv6_activate_all_interfaces="YES" and
886 ip6addrctl_policy="ipv6_prefer".
889 DTrace has grown support for userland tracing. Due to this, DTrace is
890 now i386 and amd64 only.
891 dtruss(1) is now installed by default on those systems and a new
892 kernel module is needed for userland tracing: fasttrap.
893 No changes to your kernel config file are necessary to enable
894 userland tracing, but you might consider adding 'STRIP=' and
895 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
896 to have informative userland stack traces in DTrace (ustack).
899 The acpi_aiboost(4) driver has been removed in favor of the new
900 aibs(4) driver. You should update your kernel configuration file.
903 BSD grep has been imported to the base system and it is built by
904 default. It is completely BSD licensed, highly GNU-compatible, uses
905 less memory than its GNU counterpart and has a small codebase.
906 However, it is slower than its GNU counterpart, which is mostly
907 noticeable for larger searches, for smaller ones it is measurable
908 but not significant. The reason is complex, the most important factor
909 is that we lack a modern and efficient regex library and GNU
910 overcomes this by optimizing the searches internally. Future work
911 on improving the regex performance is planned, for the meantime,
912 users that need better performance, can build GNU grep instead by
913 setting the WITH_GNU_GREP knob.
916 Due to the import of powerpc64 support, all existing powerpc kernel
917 configuration files must be updated with a machine directive like this:
918 machine powerpc powerpc
920 In addition, an updated config(8) is required to build powerpc kernels
924 A new version of ZFS (version 15) has been merged to -HEAD.
925 This version uses a python library for the following subcommands:
926 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
927 For full functionality of these commands the following port must
928 be installed: sysutils/py-zfs
931 'vm_page's are now hashed by physical address to an array of mutexes.
932 Currently this is only used to serialize access to hold_count. Over
933 time the page queue mutex will be peeled away. This changes the size
934 of pmap on every architecture. And requires all callers of vm_page_hold
935 and vm_page_unhold to be updated.
938 WITH_CTF can now be specified in src.conf (not recommended, there
939 are some problems with static executables), make.conf (would also
940 affect ports which do not use GNU make and do not override the
941 compile targets) or in the kernel config (via "makeoptions
943 When WITH_CTF was specified there before this was silently ignored,
944 so make sure that WITH_CTF is not used in places which could lead
945 to unwanted behavior.
948 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
949 to allow 32-bit compatibility on non-x86 platforms. All kernel
950 configurations on amd64 and ia64 platforms using these options must
951 be modified accordingly.
954 The utmp user accounting database has been replaced with utmpx,
955 the user accounting interface standardized by POSIX.
956 Unfortunately the semantics of utmp and utmpx don't match,
957 making it practically impossible to support both interfaces.
958 The user accounting database is used by tools like finger(1),
959 last(1), talk(1), w(1) and ac(8).
961 All applications in the base system use utmpx. This means only
962 local binaries (e.g. from the ports tree) may still use these
963 utmp database files. These applications must be rebuilt to make
966 After the system has been upgraded, it is safe to remove the old
967 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
968 assuming their contents is of no importance anymore. Old wtmp
969 databases can only be used by last(1) and ac(8) after they have
970 been converted to the new format using wtmpcvt(1).
973 Introduce the kernel thread "deadlock resolver" (which can be enabled
974 via the DEADLKRES option, see NOTES for more details) and the
975 sleepq_type() function for sleepqueues.
978 The rc.firewall and rc.firewall6 were unified, and
979 rc.firewall6 and rc.d/ip6fw were removed.
980 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
981 variables are obsoleted. Instead, the following new rc
982 variables are added to rc.d/ipfw:
984 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
985 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
986 firewall_simple_onet_ipv6, firewall_trusted_ipv6
988 The meanings correspond to the relevant IPv4 variables.
994 The default terminal emulation for syscons(4) has been changed
995 from cons25 to xterm on all platforms except pc98. This means
996 that the /etc/ttys file needs to be updated to ensure correct
997 operation of applications on the console.
999 The terminal emulation style can be toggled per window by using
1000 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1001 options can be used to change the compile-time default back to
1004 To prevent graphical artifacts, make sure the TERM environment
1005 variable is set to match the terminal emulation that is being
1006 performed by syscons(4).
1009 The layout of the structure ieee80211req_scan_result has changed.
1010 Applications that require wireless scan results (e.g. ifconfig(8))
1011 from net80211 need to be recompiled.
1013 Applications such as wpa_supplicant(8) may require a full world
1014 build without using NO_CLEAN in order to get synchronized with the
1018 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1019 There's one kernel module for each firmware. Adding "device iwnfw"
1020 to the kernel configuration file means including all three firmware
1021 images inside the kernel. If you want to include just the one for
1022 your wireless card, use the devices iwn4965fw, iwn5000fw or
1026 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1027 into rc.d/netif. The changes are the following:
1029 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1030 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1031 Note that both variables need the "inet6" keyword at the head.
1033 Do not set $ipv6_network_interfaces manually if you do not
1034 understand what you are doing. It is not needed in most cases.
1036 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1039 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1040 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1042 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1043 all configured interfaces have "inet6 accept_rtadv" in the
1044 $ifconfig_IF_ipv6. These are for backward compatibility.
1046 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1047 functionality of interfaces with no corresponding
1048 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1049 and the default address selection policy of ip6addrctl(8)
1050 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1051 Note that if you want to configure IPv6 functionality on the
1052 disabled interfaces after boot, first you need to clear the flag by
1053 using ifconfig(8) like:
1055 ifconfig em0 inet6 -ifdisabled
1057 If YES, the default address selection policy is set as
1060 The default value of $ipv6_prefer is NO.
1062 4. If your system need to receive Router Advertisement messages,
1063 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1064 scripts automatically invoke rtsol(8) when the interface becomes
1065 UP. The Router Advertisement messages are used for SLAAC
1066 (State-Less Address AutoConfiguration).
1069 802.11s D3.03 support was committed. This is incompatible with the
1070 previous code, which was based on D3.0.
1073 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1074 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1075 control whether accepting Router Advertisement messages or not.
1076 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1077 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1078 The ifconfig(8) utility now supports these flags.
1081 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1082 mount(8) and -a option for df(1) to see them.
1085 The old tunable hw.bus.devctl_disable has been superseded by
1086 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1087 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1091 Remove the option STOP_NMI. The default action is now to use NMI only
1092 for KDB via the newly introduced function stop_cpus_hard() and
1093 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1096 The stable/8 branch created in subversion. This corresponds to the
1097 RELENG_8 branch in CVS.
1100 Bump the shared library version numbers for all libraries that do not
1101 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1102 __FreeBSD_version to 800105.
1105 Due to changes in the implementation of virtual network stack support,
1106 all network-related kernel modules must be recompiled. As this change
1107 breaks the ABI, bump __FreeBSD_version to 800104.
1110 The TOE interface to the TCP syncache has been modified to remove
1111 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1112 The cxgb driver is the only TOE consumer affected by this change, and
1113 needs to be recompiled along with the kernel. As this change breaks
1114 the ABI, bump __FreeBSD_version to 800103.
1117 Padding has been added to struct tcpcb, sackhint and tcpstat in
1118 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1119 maintaining the ABI. However, this change breaks the ABI, so bump
1120 __FreeBSD_version to 800102. User space tools that rely on the size of
1121 any of these structs (e.g. sockstat) need to be recompiled.
1124 The NFS_LEGACYRPC option has been removed along with the old kernel
1125 RPC implementation that this option selected. Kernel configurations
1126 may need to be adjusted.
1129 The network interface device nodes at /dev/net/<interface> have been
1130 removed. All ioctl operations can be performed the normal way using
1131 routing sockets. The kqueue functionality can generally be replaced
1132 with routing sockets.
1135 The documentation from the FreeBSD Documentation Project (Handbook,
1136 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1137 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1140 The ABI of various structures related to the SYSV IPC API have been
1141 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1142 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1146 Layout of struct vnet has changed as routing related variables were
1147 moved to their own Vimage module. Modules need to be recompiled. Bump
1148 __FreeBSD_version to 800099.
1151 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1152 respectively. As long as no more than 16 groups per process are used,
1153 no changes should be visible. When more than 16 groups are used, old
1154 binaries may fail if they call getgroups() or getgrouplist() with
1155 statically sized storage. Recompiling will work around this, but
1156 applications should be modified to use dynamically allocated storage
1157 for group arrays as POSIX.1-2008 does not cap an implementation's
1158 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1160 NFS and portalfs mounts may also be affected as the list of groups is
1161 truncated to 16. Users of NFS who use more than 16 groups, should
1162 take care that negative group permissions are not used on the exported
1163 file systems as they will not be reliable unless a GSSAPI based
1164 authentication method is used.
1167 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1168 option compiles in the support for adaptive spinning for lockmgrs
1169 which want to enable it. The lockinit() function now accepts the flag
1170 LK_ADAPTIVE in order to make the lock object subject to adaptive
1171 spinning when both held in write and read mode.
1174 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1175 changed. User applications that use this ioctl need to be rebuilt.
1178 The layout of struct thread has changed. Kernel and modules need to
1182 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1183 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1186 window(1) has been removed from the base system. It can now be
1187 installed from ports. The port is called misc/window.
1190 The way we are storing and accessing `routing table' entries has
1191 changed. Programs reading the FIB, like netstat, need to be
1195 A new netisr implementation has been added for FreeBSD 8. Network
1196 file system modules, such as igmp, ipdivert, and others, should be
1198 Bump __FreeBSD_version to 800096.
1201 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1205 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1206 Bump __FreeBSD_version to 800094.
1209 Add mnt_xflag field to 'struct mount'. File system modules need to be
1211 Bump __FreeBSD_version to 800093.
1214 The compiling option ADAPTIVE_SX has been retired while it has been
1215 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1216 The KPI for sx_init_flags() changes as accepting flags:
1217 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1218 been introduced in order to handle the reversed logic.
1219 Bump __FreeBSD_version to 800092.
1222 Add support for hierarchical jails. Remove global securelevel.
1223 Bump __FreeBSD_version to 800091.
1226 The layout of struct vnet_net has changed, therefore modules
1228 Bump __FreeBSD_version to 800090.
1231 The newly imported zic(8) produces a new format in the output. Please
1232 run tzsetup(8) to install the newly created data to /etc/localtime.
1235 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1236 hw.usb.* and is now consistent again with previous releases.
1239 802.11 monitor mode support was revised and driver api's were changed.
1240 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1241 of DLT_IEEE802_11. No user-visible data structures were changed but
1242 applications that use DLT_IEEE802_11 may require changes.
1243 Bump __FreeBSD_version to 800088.
1246 The layout of the following structs has changed: sysctl_oid,
1247 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1248 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1249 panics may be experienced. World rebuild is required for
1250 correctly checking networking state from userland.
1251 Bump __FreeBSD_version to 800085.
1254 MLDv2 and Source-Specific Multicast (SSM) have been merged
1255 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1256 The implementation of SSM within FreeBSD's IPv6 stack closely
1257 follows the IPv4 implementation.
1259 For kernel developers:
1261 * The most important changes are that the ip6_output() and
1262 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1263 and this lock has been downgraded to a non-recursive mutex.
1265 * As with the changes to the IPv4 stack to support SSM, filtering
1266 of inbound multicast traffic must now be performed by transport
1267 protocols within the IPv6 stack. This does not apply to TCP and
1268 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1270 * The KPIs used by IPv6 multicast are similar to those used by
1271 the IPv4 stack, with the following differences:
1272 * im6o_mc_filter() is analogous to imo_multicast_filter().
1273 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1274 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1275 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1276 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1277 for MLDv1 have an additional 'timer' argument which is used to
1278 jitter the initial membership report for the solicited-node
1279 multicast membership on-link.
1280 * This is not strictly needed for MLDv2, which already jitters
1281 its report transmissions. However, the 'timer' argument is
1282 preserved in case MLDv1 is active on the interface.
1284 * The KAME linked-list based IPv6 membership implementation has
1285 been refactored to use a vector similar to that used by the IPv4
1287 Code which maintains a list of its own multicast memberships
1288 internally, e.g. carp, has been updated to reflect the new
1291 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1292 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1293 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1294 implementation constraint which needs to be addressed in HEAD.
1296 For application developers:
1298 * The changes are broadly similar to those made for the IPv4
1301 * The use of IPv4 and IPv6 multicast socket options on the same
1302 socket, using mapped addresses, HAS NOT been tested or supported.
1304 * There are a number of issues with the implementation of various
1305 IPv6 multicast APIs which need to be resolved in the API surface
1306 before the implementation is fully compatible with KAME userland
1307 use, and these are mostly to do with interface index treatment.
1309 * The literature available discusses the use of either the delta / ASM
1310 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1311 using setsourcefilter(3)/getsourcefilter(3). For more information
1312 please refer to RFC 3768, 'Socket Interface Extensions for
1313 Multicast Source Filters'.
1315 * Applications which use the published RFC 3678 APIs should be fine.
1317 For systems administrators:
1319 * The mtest(8) utility has been refactored to support IPv6, in
1320 addition to IPv4. Interface addresses are no longer accepted
1321 as arguments, their names must be used instead. The utility
1322 will map the interface name to its first IPv4 address as
1323 returned by getifaddrs(3).
1325 * The ifmcstat(8) utility has also been updated to print the MLDv2
1326 endpoint state and source filter lists via sysctl(3).
1328 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1329 loopback of IPv6 multicast datagrams by default; it defaults to 1
1330 to preserve the existing behaviour. Disabling multicast loopback is
1331 recommended for optimal system performance.
1333 * The IPv6 MROUTING code has been changed to examine this sysctl
1334 instead of attempting to perform a group lookup before looping
1335 back forwarded datagrams.
1337 Bump __FreeBSD_version to 800084.
1340 Implement low-level Bluetooth HCI API.
1341 Bump __FreeBSD_version to 800083.
1344 The layout of struct malloc_type, used by modules to register new
1345 memory allocation types, has changed. Most modules will need to
1346 be rebuilt or panics may be experienced.
1347 Bump __FreeBSD_version to 800081.
1350 Anticipate overflowing inp_flags - add inp_flags2.
1351 This changes most offsets in inpcb, so checking v4 connection
1352 state will require a world rebuild.
1353 Bump __FreeBSD_version to 800080.
1356 Add an llentry to struct route and struct route_in6. Modules
1357 embedding a struct route will need to be recompiled.
1358 Bump __FreeBSD_version to 800079.
1361 The size of rt_metrics_lite and by extension rtentry has changed.
1362 Networking administration apps will need to be recompiled.
1363 The route command now supports show as an alias for get, weighting
1364 of routes, sticky and nostick flags to alter the behavior of stateful
1366 Bump __FreeBSD_version to 800078.
1369 Do not use Giant for kbdmux(4) locking. This is wrong and
1370 apparently causing more problems than it solves. This will
1371 re-open the issue where interrupt handlers may race with
1372 kbdmux(4) in polling mode. Typical symptoms include (but
1373 not limited to) duplicated and/or missing characters when
1374 low level console functions (such as gets) are used while
1375 interrupts are enabled (for example geli password prompt,
1376 mountroot prompt etc.). Disabling kbdmux(4) may help.
1379 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1380 kernel modules referencing any of the above need to be recompiled.
1381 Bump __FreeBSD_version to 800075.
1384 GEOM_PART has become the default partition slicer for storage devices,
1385 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1386 introduces some changes:
1388 MSDOS/EBR: the devices created from MSDOS extended partition entries
1389 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1390 to devices with offset-based names. fstabs may need to be modified.
1392 BSD: the "geometry does not match label" warning is harmless in most
1393 cases but it points to problems in file system misalignment with
1394 disk geometry. The "c" partition is now implicit, covers the whole
1395 top-level drive and cannot be (mis)used by users.
1397 General: Kernel dumps are now not allowed to be written to devices
1398 whose partition types indicate they are meant to be used for file
1399 systems (or, in case of MSDOS partitions, as something else than
1402 Most of these changes date approximately from 200812.
1405 The uscanner(4) driver has been removed from the kernel. This follows
1406 Linux removing theirs in 2.6 and making libusb the default interface
1407 (supported by sane).
1410 The multicast forwarding code has been cleaned up. netstat(1)
1411 only relies on KVM now for printing bandwidth upcall meters.
1412 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1413 ip6_mroute_mod respectively. The config(5) options for statically
1414 compiling this code remain the same, i.e. 'options MROUTING'.
1417 Support for the IFF_NEEDSGIANT network interface flag has been
1418 removed, which means that non-MPSAFE network device drivers are no
1419 longer supported. In particular, if_ar, if_sr, and network device
1420 drivers from the old (legacy) USB stack can no longer be built or
1424 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1425 a bunch of new language catalog files have also been added.
1426 This means that some common libc messages are now localized and
1427 they depend on the LC_MESSAGES environmental variable.
1430 The k8temp(4) driver has been renamed to amdtemp(4) since
1431 support for Family 10 and Family 11 CPU families was added.
1434 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1435 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1437 For kernel developers, the most important changes are that the
1438 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1439 and this lock has been downgraded to a non-recursive mutex.
1441 Transport protocols (UDP, Raw IP) are now responsible for filtering
1442 inbound multicast traffic according to group membership and source
1443 filters. The imo_multicast_filter() KPI exists for this purpose.
1444 Transports which do not use multicast (SCTP, TCP) already reject
1445 multicast by default. Forwarding and receive performance may improve
1446 as a mutex acquisition is no longer needed in the ip_input()
1447 low-level input path. in_addmulti() and in_delmulti() are shimmed
1448 to new KPIs which exist to support SSM in-kernel.
1450 For application developers, it is recommended that loopback of
1451 multicast datagrams be disabled for best performance, as this
1452 will still cause the lock to be taken for each looped-back
1453 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1454 be tuned to 0 to disable loopback by default; it defaults to 1
1455 to preserve the existing behaviour.
1457 For systems administrators, to obtain best performance with
1458 multicast reception and multiple groups, it is always recommended
1459 that a card with a suitably precise hash filter is used. Hash
1460 collisions will still result in the lock being taken within the
1461 transport protocol input path to check group membership.
1463 If deploying FreeBSD in an environment with IGMP snooping switches,
1464 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1465 enabled; this forces 224.0.0.0/24 group membership to be announced
1468 The size of 'struct igmpstat' has changed; netstat needs to be
1469 recompiled to reflect this.
1470 Bump __FreeBSD_version to 800070.
1473 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1474 updated to use it. This requires a buildworld/installworld in order to
1475 update the library and dependencies (usbconfig, etc). Its advisable to
1476 rebuild all ports which uses libusb. More specific directions are given
1477 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1478 libusb are no longer required and can be removed.
1481 A workaround is committed to allow the creation of System V shared
1482 memory segment of size > 2 GB on the 64-bit architectures.
1483 Due to a limitation of the existing ABI, the shm_segsz member
1484 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1485 wrong for large segments. Note that limits must be explicitly
1486 raised to allow such segments to be created.
1489 The layout of struct ifnet has changed, requiring a rebuild of all
1490 network device driver modules.
1493 The /dev handling for the new USB stack has changed, a
1494 buildworld/installworld is required for libusb20.
1497 The new USB2 stack has now been permanently moved in and all kernel and
1498 module names reverted to their previous values (eg, usb, ehci, ohci,
1499 ums, ...). The old usb stack can be compiled in by prefixing the name
1500 with the letter 'o', the old usb modules have been removed.
1501 Updating entry 20090216 for xorg and 20090215 for libmap may still
1505 The rc.conf(5) option if_up_delay has been renamed to
1506 defaultroute_delay to better reflect its purpose. If you have
1507 customized this setting in /etc/rc.conf you need to update it to
1511 xorg 7.4 wants to configure its input devices via hald which does not
1512 yet work with USB2. If the keyboard/mouse does not work in xorg then
1514 Option "AllowEmptyInput" "off"
1515 to your ServerLayout section. This will cause X to use the configured
1516 kbd and mouse sections from your xorg.conf.
1519 The GENERIC kernels for all architectures now default to the new USB2
1520 stack. No kernel config options or code have been removed so if a
1521 problem arises please report it and optionally revert to the old USB
1522 stack. If you are loading USB kernel modules or have a custom kernel
1523 that includes GENERIC then ensure that usb names are also changed over,
1524 eg uftdi -> usb2_serial_ftdi.
1526 Older programs linked against the ports libusb 0.1 need to be
1527 redirected to the new stack's libusb20. /etc/libmap.conf can
1529 # Map old usb library to new one for usb2 stack
1530 libusb-0.1.so.8 libusb20.so.1
1533 All USB ethernet devices now attach as interfaces under the name ueN
1534 (eg. ue0). This is to provide a predictable name as vendors often
1535 change usb chipsets in a product without notice.
1538 The ichsmb(4) driver has been changed to require SMBus slave
1539 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1540 All of the other SMBus controller drivers require left-justified
1541 slave addresses, so this change makes all the drivers provide the
1545 INET6 statistics (struct ip6stat) was updated.
1546 netstat(1) needs to be recompiled.
1549 NTFS has been removed from GENERIC kernel on amd64 to match
1550 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1551 will load ntfs.ko module automatically when NTFS support is
1552 actually needed, unless ntfs.ko is not installed or security
1553 level prohibits loading kernel modules. If either is the case,
1554 "options NTFS" has to be added into kernel config.
1557 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1558 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1559 800061. User space tools that rely on the size of struct tcpcb in
1560 tcp_var.h (e.g. sockstat) need to be recompiled.
1563 ng_tty(4) module updated to match the new TTY subsystem.
1564 Due to API change, user-level applications must be updated.
1565 New API support added to mpd5 CVS and expected to be present
1566 in next mpd5.3 release.
1569 With __FreeBSD_version 800060 the makefs tool is part of
1570 the base system (it was a port).
1573 The afdata and ifnet locks have been changed from mutexes to
1574 rwlocks, network modules will need to be re-compiled.
1577 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1578 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1579 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1580 architecture and 40 bytes on 64-bit architecture. The userland
1581 applications "arp" and "ndp" have been updated accordingly.
1582 The output from "netstat -r" shows only routing entries and
1583 none of the L2 information.
1586 __FreeBSD_version 800057 marks the switchover from the
1587 binary ath hal to source code. Users must add the line:
1589 options AH_SUPPORT_AR5416
1591 to their kernel config files when specifying:
1595 The ath_hal module no longer exists; the code is now compiled
1596 together with the driver in the ath module. It is now
1597 possible to tailor chip support (i.e. reduce the set of chips
1598 and thereby the code size); consult ath_hal(4) for details.
1601 __FreeBSD_version 800054 adds memory barriers to
1602 <machine/atomic.h>, new interfaces to ifnet to facilitate
1603 multiple hardware transmit queues for cards that support
1604 them, and a lock-less ring-buffer implementation to
1605 enable drivers to more efficiently manage queueing of
1609 A new version of ZFS (version 13) has been merged to -HEAD.
1610 This version has zpool attribute "listsnapshots" off by
1611 default, which means "zfs list" does not show snapshots,
1612 and is the same as Solaris behavior.
1615 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1618 The uhci, ohci, ehci and slhci USB Host controller drivers have
1619 been put into separate modules. If you load the usb module
1620 separately through loader.conf you will need to load the
1621 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1622 controller add the following to loader.conf:
1628 The ABI used by the PMC toolset has changed. Please keep
1629 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1633 atapci kernel module now includes only generic PCI ATA
1634 driver. AHCI driver moved to ataahci kernel module.
1635 All vendor-specific code moved into separate kernel modules:
1636 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1637 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1638 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1639 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1642 The TTY subsystem of the kernel has been replaced by a new
1643 implementation, which provides better scalability and an
1644 improved driver model. Most common drivers have been migrated to
1645 the new TTY subsystem, while others have not. The following
1646 drivers have not yet been ported to the new TTY layer:
1649 cy, digi, rc, rp, sio
1655 ng_h4, ng_tty, ppp, sl, snp
1657 Adding these drivers to your kernel configuration file shall
1658 cause compilation to fail.
1661 ntpd has been upgraded to 4.2.4p5.
1664 OpenSSH has been upgraded to 5.1p1.
1666 For many years, FreeBSD's version of OpenSSH preferred DSA
1667 over RSA for host and user authentication keys. With this
1668 upgrade, we've switched to the vendor's default of RSA over
1669 DSA. This may cause upgraded clients to warn about unknown
1670 host keys even for previously known hosts. Users should
1671 follow the usual procedure for verifying host keys before
1672 accepting the RSA key.
1674 This can be circumvented by setting the "HostKeyAlgorithms"
1675 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1678 Please note that the sequence of keys offered for
1679 authentication has been changed as well. You may want to
1680 specify IdentityFile in a different order to revert this
1684 The sio(4) driver has been removed from the i386 and amd64
1685 kernel configuration files. This means uart(4) is now the
1686 default serial port driver on those platforms as well.
1688 To prevent collisions with the sio(4) driver, the uart(4) driver
1689 uses different names for its device nodes. This means the
1690 onboard serial port will now most likely be called "ttyu0"
1691 instead of "ttyd0". You may need to reconfigure applications to
1692 use the new device names.
1694 When using the serial port as a boot console, be sure to update
1695 /boot/device.hints and /etc/ttys before booting the new kernel.
1696 If you forget to do so, you can still manually specify the hints
1697 at the loader prompt:
1699 set hint.uart.0.at="isa"
1700 set hint.uart.0.port="0x3F8"
1701 set hint.uart.0.flags="0x10"
1702 set hint.uart.0.irq="4"
1706 The gpt(8) utility has been removed. Use gpart(8) to partition
1710 The version that Linuxulator emulates was changed from 2.4.2
1711 to 2.6.16. If you experience any problems with Linux binaries
1712 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1713 if it fixes the problem contact emulation mailing list.
1716 ISDN4BSD (I4B) was removed from the src tree. You may need to
1717 update a your kernel configuration and remove relevant entries.
1720 I have checked in code to support multiple routing tables.
1721 See the man pages setfib(1) and setfib(2).
1722 This is a hopefully backwards compatible version,
1723 but to make use of it you need to compile your kernel
1724 with options ROUTETABLES=2 (or more up to 16).
1727 The 802.11 wireless support was redone to enable multi-bss
1728 operation on devices that are capable. The underlying device
1729 is no longer used directly but instead wlanX devices are
1730 cloned with ifconfig. This requires changes to rc.conf files.
1731 For example, change:
1732 ifconfig_ath0="WPA DHCP"
1735 ifconfig_wlan0="WPA DHCP"
1736 see rc.conf(5) for more details. In addition, mergemaster of
1737 /etc/rc.d is highly recommended. Simultaneous update of userland
1738 and kernel wouldn't hurt either.
1740 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1741 modules were merged into the base wlan module. All references
1742 to these modules (e.g. in kernel config files) must be removed.
1745 psm(4) has gained write(2) support in native operation level.
1746 Arbitrary commands can be written to /dev/psm%d and status can
1747 be read back from it. Therefore, an application is responsible
1748 for status validation and error recovery. It is a no-op in
1749 other operation levels.
1752 Support for KSE threading has been removed from the kernel. To
1753 run legacy applications linked against KSE libmap.conf may
1754 be used. The following libmap.conf may be used to ensure
1755 compatibility with any prior release:
1757 libpthread.so.1 libthr.so.1
1758 libpthread.so.2 libthr.so.2
1759 libkse.so.3 libthr.so.3
1762 The layout of struct vmspace has changed. This affects libkvm
1763 and any executables that link against libkvm and use the
1764 kvm_getprocs() function. In particular, but not exclusively,
1765 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1766 The effects are minimal, but it's advisable to upgrade world
1770 The latest em driver no longer has support in it for the
1771 82575 adapter, this is now moved to the igb driver. The
1772 split was done to make new features that are incompatible
1773 with older hardware easier to do.
1776 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1777 likewise the kernel option is now GEOM_LINUX_LVM.
1780 The default NFS mount mode has changed from UDP to TCP for
1781 increased reliability. If you rely on (insecurely) NFS
1782 mounting across a firewall you may need to update your
1786 Belatedly note the addition of m_collapse for compacting
1790 The fts(3) structures have been changed to use adequate
1791 integer types for their members and so to be able to cope
1792 with huge file trees. The old fts(3) ABI is preserved
1793 through symbol versioning in libc, so third-party binaries
1794 using fts(3) should still work, although they will not take
1795 advantage of the extended types. At the same time, some
1796 third-party software might fail to build after this change
1797 due to unportable assumptions made in its source code about
1798 fts(3) structure members. Such software should be fixed
1799 by its vendor or, in the worst case, in the ports tree.
1800 FreeBSD_version 800015 marks this change for the unlikely
1801 case that a portable fix is impossible.
1804 To upgrade to -current after this date, you must be running
1805 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1806 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1809 The ADAPTIVE_GIANT kernel option has been retired because its
1810 functionality is the default now.
1813 The AT keyboard emulation of sunkbd(4) has been turned on
1814 by default. In order to make the special symbols of the Sun
1815 keyboards driven by sunkbd(4) work under X these now have
1816 to be configured the same way as Sun USB keyboards driven
1817 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1819 Option "XkbLayout" "us"
1820 Option "XkbRules" "xorg"
1821 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1824 It has been decided that it is desirable to provide ABI
1825 backwards compatibility to the FreeBSD 4/5/6 versions of the
1826 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1827 broken with the introduction of PCI domain support (see the
1828 20070930 entry). Unfortunately, this required the ABI of
1829 PCIOCGETCONF to be broken again in order to be able to
1830 provide backwards compatibility to the old version of that
1831 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1832 again. As for prominent ports this affects neither pciutils
1833 nor xorg-server this time, the hal port needs to be rebuilt
1837 The misnamed kthread_create() and friends have been renamed
1838 to kproc_create() etc. Many of the callers already
1839 used kproc_start()..
1840 I will return kthread_create() and friends in a while
1841 with implementations that actually create threads, not procs.
1842 Renaming corresponds with version 800002.
1851 Avoid using make -j when upgrading. While generally safe, there are
1852 sometimes problems using -j to upgrade. If your upgrade fails with
1853 -j, please try again without -j. From time to time in the past there
1854 have been problems using -j with buildworld and/or installworld. This
1855 is especially true when upgrading between "distant" versions (eg one
1856 that cross a major release boundary or several minor releases, or when
1857 several months have passed on the -current branch).
1859 Sometimes, obscure build problems are the result of environment
1860 poisoning. This can happen because the make utility reads its
1861 environment when searching for values for global variables. To run
1862 your build attempts in an "environmental clean room", prefix all make
1863 commands with 'env -i '. See the env(1) manual page for more details.
1865 When upgrading from one major version to another it is generally best
1866 to upgrade to the latest code in the currently installed branch first,
1867 then do an upgrade to the new branch. This is the best-tested upgrade
1868 path, and has the highest probability of being successful. Please try
1869 this approach before reporting problems with a major version upgrade.
1871 When upgrading a live system, having a root shell around before
1872 installing anything can help undo problems. Not having a root shell
1873 around can lead to problems if pam has changed too much from your
1874 starting point to allow continued authentication after the upgrade.
1878 When upgrading the boot ZFS pool to a new version, always follow
1881 1.) recompile and reinstall the ZFS boot loader and boot block
1882 (this is part of "make buildworld" and "make installworld")
1884 2.) update the ZFS boot block on your boot drive
1886 The following example updates the ZFS boot block on the first
1887 partition (freebsd-boot) of a GPT partitioned drive ad0:
1888 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1890 Non-boot pools do not need these updates.
1894 If you are updating from a prior version of FreeBSD (even one just
1895 a few days old), you should follow this procedure. It is the most
1896 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1898 make kernel-toolchain
1899 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1900 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1902 To test a kernel once
1903 ---------------------
1904 If you just want to boot a kernel once (because you are not sure
1905 if it works, or if you want to boot a known bad kernel to provide
1906 debugging information) run
1907 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1908 nextboot -k testkernel
1910 To just build a kernel when you know that it won't mess you up
1911 --------------------------------------------------------------
1912 This assumes you are already running a CURRENT system. Replace
1913 ${arch} with the architecture of your machine (e.g. "i386",
1914 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1916 cd src/sys/${arch}/conf
1917 config KERNEL_NAME_HERE
1918 cd ../compile/KERNEL_NAME_HERE
1923 If this fails, go to the "To build a kernel" section.
1925 To rebuild everything and install it on the current system.
1926 -----------------------------------------------------------
1927 # Note: sometimes if you are running current you gotta do more than
1928 # is listed here if you are upgrading from a really old current.
1930 <make sure you have good level 0 dumps>
1932 make kernel KERNCONF=YOUR_KERNEL_HERE
1934 <reboot in single user> [3]
1941 To cross-install current onto a separate partition
1942 --------------------------------------------------
1943 # In this approach we use a separate partition to hold
1944 # current's root, 'usr', and 'var' directories. A partition
1945 # holding "/", "/usr" and "/var" should be about 2GB in
1948 <make sure you have good level 0 dumps>
1951 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1952 <maybe newfs current's root partition>
1953 <mount current's root partition on directory ${CURRENT_ROOT}>
1954 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1955 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1956 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1957 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1958 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1959 <reboot into current>
1960 <do a "native" rebuild/install as described in the previous section>
1961 <maybe install compatibility libraries from ports/misc/compat*>
1965 To upgrade in-place from stable to current
1966 ----------------------------------------------
1967 <make sure you have good level 0 dumps>
1969 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1971 <reboot in single user> [3]
1978 Make sure that you've read the UPDATING file to understand the
1979 tweaks to various things you need. At this point in the life
1980 cycle of current, things change often and you are on your own
1981 to cope. The defaults can also change, so please read ALL of
1982 the UPDATING entries.
1984 Also, if you are tracking -current, you must be subscribed to
1985 freebsd-current@freebsd.org. Make sure that before you update
1986 your sources that you have read and understood all the recent
1987 messages there. If in doubt, please track -stable which has
1988 much fewer pitfalls.
1990 [1] If you have third party modules, such as vmware, you
1991 should disable them at this point so they don't crash your
1994 [3] From the bootblocks, boot -s, and then do
1999 adjkerntz -i # if CMOS is wall time
2000 Also, when doing a major release upgrade, it is required that
2001 you boot into single user mode to do the installworld.
2003 [4] Note: This step is non-optional. Failure to do this step
2004 can result in a significant reduction in the functionality of the
2005 system. Attempting to do it by hand is not recommended and those
2006 that pursue this avenue should read this file carefully, as well
2007 as the archives of freebsd-current and freebsd-hackers mailing lists
2008 for potential gotchas. The -U option is also useful to consider.
2009 See mergemaster(8) for more information.
2011 [5] Usually this step is a noop. However, from time to time
2012 you may need to do this if you get unknown user in the following
2013 step. It never hurts to do it all the time. You may need to
2014 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2015 install) after the buildworld before this step if you last updated
2016 from current before 20130425 or from -stable before 20130430.
2018 [6] This only deletes old files and directories. Old libraries
2019 can be deleted by "make delete-old-libs", but you have to make
2020 sure that no program is using those libraries anymore.
2022 [8] In order to have a kernel that can run the 4.x binaries needed to
2023 do an installworld, you must include the COMPAT_FREEBSD4 option in
2024 your kernel. Failure to do so may leave you with a system that is
2025 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2026 required to run the 5.x binaries on more recent kernels. And so on
2027 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2029 Make sure that you merge any new devices from GENERIC since the
2030 last time you updated your kernel config file.
2032 [9] When checking out sources, you must include the -P flag to have
2033 cvs prune empty directories.
2035 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2036 "?=" instead of the "=" assignment operator, so that buildworld can
2037 override the CPUTYPE if it needs to.
2039 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2040 not on the command line, or in /etc/make.conf. buildworld will
2041 warn if it is improperly defined.
2044 This file contains a list, in reverse chronological order, of major
2045 breakages in tracking -current. It is not guaranteed to be a complete
2046 list of such breakages, and only contains entries since October 10, 2007.
2047 If you need to see UPDATING entries from before that date, you will need
2048 to fetch an UPDATING file from an older FreeBSD release.
2050 Copyright information:
2052 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2054 Redistribution, publication, translation and use, with or without
2055 modification, in full or in part, in any form or format of this
2056 document are permitted without further permission from the author.
2058 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2059 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2060 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2061 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2062 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2063 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2064 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2065 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2066 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2067 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2068 POSSIBILITY OF SUCH DAMAGE.
2070 Contact Warner Losh if you have any questions about your use of