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 10.x IS SLOW:
20 FreeBSD 10.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 The PROCDESC kernel option is now part of the GENERIC kernel
36 configuration and is required for the rwhod(8) to work.
37 If you are using custom kernel configuration, you should include
41 The API and ABI related to the Capsicum framework was modified
42 in backward incompatible way. The userland libraries and programs
43 have to be recompiled to work with the new kernel. This includes the
44 following libraries and programs, but the whole buildworld is
45 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
46 kdump, procstat, rwho, rwhod, uniq.
49 Thomas Dickey (vendor author thereof) reports that dialog(1) since
50 2011/10/18 has a bug in handling --hline. Testers and I noticed the
51 --hline is not ignored but displayed as a NULL string, regardless of
52 value. This will cause confusion in some bsdconfig dialogs where the
53 --hline is used to inform users which keybindings to use. This will
54 likewise affect any other persons relying on --hline. It also looks
55 rather strange seeing "[]" at the bottom of dialog(1) widgets when
56 passing --hline "anything". Thomas said he will have a look in a few
57 weeks. NOTE: The "[]" brackets appear with the left-edge where it
58 would normally appear given the width of text to display, but the
59 displayed text is not there (part of the bug).
62 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
63 Thus "device padlock_rng" and "device rdrand_rng" should be
64 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
67 WITH_ICONV has been split into two feature sets. WITH_ICONV now
68 enables just the iconv* functionality and is now on by default.
69 WITH_LIBICONV_COMPAT enables the libiconv api and link time
70 compatability. Set WITHOUT_ICONV to build the old way.
71 If you have been using WITH_ICONV before, you will very likely
72 need to turn on WITH_LIBICONV_COMPAT.
75 INVARIANTS option now enables DEBUG for code with OpenSolaris and
76 Illumos origin, including ZFS. If you have INVARIANTS in your
77 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
79 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
80 locks if WITNESS option was set. Because that generated a lot of
81 witness(9) reports and all of them were believed to be false
82 positives, this is no longer done. New option OPENSOLARIS_WITNESS
83 can be used to achieve the previous behavior.
86 Timer values in IPv6 data structures now use time_uptime instead
87 of time_second. Although this is not a user-visible functional
88 change, userland utilities which directly use them---ndp(8),
89 rtadvd(8), and rtsold(8) in the base system---need to be updated
93 find -delete can now delete the pathnames given as arguments,
94 instead of only files found below them or if the pathname did
95 not contain any slashes. Formerly, the following error message
98 find: -delete: <path>: relative path potentially not safe
100 Deleting the pathnames given as arguments can be prevented
101 without error messages using -mindepth 1 or by changing
102 directory and passing "." as argument to find. This works in the
103 old as well as the new version of find.
106 Behavior of devfs rules path matching has been changed.
107 Pattern is now always matched against fully qualified devfs
108 path and slash characters must be explicitly matched by
109 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
110 subdirectories must be reviewed.
113 The default ARM ABI has changed to the ARM EABI. The old ABI is
114 incompatible with the ARM EABI and all programs and modules will
115 need to be rebuilt to work with a new kernel.
117 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
119 NOTE: Support for the old ABI will be removed in the future and
120 users are advised to upgrade.
123 pkg_install has been disconnected from the build if you really need it
124 you should add WITH_PKGTOOLS in your src.conf(5).
127 Most of network statistics structures were changed to be able
128 keep 64-bits counters. Thus all tools, that work with networking
129 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
132 Fix targets that run multiple make's to use && rather than ;
133 so that subsequent steps depend on success of previous.
135 NOTE: if building 'universe' with -j* on stable/8 or stable/9
136 it would be better to start the build using bmake, to avoid
137 overloading the machine.
140 Fix a bug that allowed a tracing process (e.g. gdb) to write
141 to a memory-mapped file in the traced process's address space
142 even if neither the traced process nor the tracing process had
143 write access to that file.
146 CVS has been removed from the base system. An exact copy
147 of the code is available from the devel/cvs port.
150 Some people report the following error after the switch to bmake:
152 make: illegal option -- J
153 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
155 *** [buildworld] Error code 2
157 this likely due to an old instance of make in
158 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
159 which src/Makefile will use that blindly, if it exists, so if
160 you see the above error:
162 rm -rf `make -V MAKEPATH`
167 Use bmake by default.
168 Whereas before one could choose to build with bmake via
169 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
170 make. The goal is to remove these knobs for 10-RELEASE.
172 It is worth noting that bmake (like gmake) treats the command
173 line as the unit of failure, rather than statements within the
174 command line. Thus '(cd some/where && dosomething)' is safer
175 than 'cd some/where; dosomething'. The '()' allows consistent
176 behavior in parallel build.
179 Fix a bug that allows NFS clients to issue READDIR on files.
182 The WITHOUT_IDEA option has been removed because
183 the IDEA patent expired.
186 The sysctl which controls TRIM support under ZFS has been renamed
187 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
191 The mergemaster command now uses the default MAKEOBJDIRPREFIX
192 rather than creating it's own in the temporary directory in
193 order allow access to bootstrapped versions of tools such as
194 install and mtree. When upgrading from version of FreeBSD where
195 the install command does not support -l, you will need to
196 install a new mergemaster command if mergemaster -p is required.
197 This can be accomplished with the command (cd src/usr.sbin/mergemaster
201 Legacy ATA stack, disabled and replaced by new CAM-based one since
202 FreeBSD 9.0, completely removed from the sources. Kernel modules
203 atadisk and atapi*, user-level tools atacontrol and burncd are
204 removed. Kernel option `options ATA_CAM` is now permanently enabled
208 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
209 and socketpair(2). Software, in particular Kerberos, may
210 automatically detect and use these during building. The resulting
211 binaries will not work on older kernels.
214 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
215 information, see the respective 20130304 entry).
218 Recent commits to callout(9) changed the size of struct callout,
219 so the KBI is probably heavily disturbed. Also, some functions
220 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
221 by macros. Every kernel module using it won't load, so rebuild
224 The ctl device has been re-enabled in GENERIC for i386 and amd64,
225 but does not initialize by default (because of the new CTL_DISABLE
226 option) to save memory. To re-enable it, remove the CTL_DISABLE
227 option from the kernel config file or set kern.cam.ctl.disable=0
228 in /boot/loader.conf.
231 The ctl device has been disabled in GENERIC for i386 and amd64.
232 This was done due to the extra memory being allocated at system
233 initialisation time by the ctl driver which was only used if
234 a CAM target device was created. This makes a FreeBSD system
235 unusable on 128MB or less of RAM.
238 A new compression method (lz4) has been merged to -HEAD. Please
239 refer to zpool-features(7) for more information.
241 Please refer to the "ZFS notes" section of this file for information
242 on upgrading boot ZFS pools.
245 A BSD-licensed patch(1) variant has been added and is installed
246 as bsdpatch, being the GNU version the default patch.
247 To inverse the logic and use the BSD-licensed one as default,
248 while having the GNU version installed as gnupatch, rebuild
249 and install world with the WITH_BSD_PATCH knob set.
252 Due to the use of the new -l option to install(1) during build
253 and install, you must take care not to directly set the INSTALL
254 make variable in your /etc/make.conf, /etc/src.conf, or on the
255 command line. If you wish to use the -C flag for all installs
256 you may be able to add INSTALL+=-C to /etc/make.conf or
260 The install(1) option -M has changed meaning and now takes an
261 argument that is a file or path to append logs to. In the
262 unlikely event that -M was the last option on the command line
263 and the command line contained at least two files and a target
264 directory the first file will have logs appended to it. The -M
265 option served little practical purpose in the last decade so its
266 use is expected to be extremely rare.
269 After switching to Clang as the default compiler some users of ZFS
270 on i386 systems started to experience stack overflow kernel panics.
271 Please consider using 'options KSTACK_PAGES=4' in such configurations.
274 GEOM_LABEL now mangles label names read from file system metadata.
275 Mangling affect labels containing spaces, non-printable characters,
276 '%' or '"'. Device names in /etc/fstab and other places may need to
280 By default, only the 10 most recent kernel dumps will be saved. To
281 restore the previous behaviour (no limit on the number of kernel dumps
282 stored in the dump directory) add the following line to /etc/rc.conf:
287 With the addition of auditdistd(8), a new auditdistd user is now
288 depended on during installworld. "mergemaster -p" can be used to add
289 the user prior to installworld, as documented in the handbook.
292 The sin6_scope_id member variable in struct sockaddr_in6 is now
293 filled by the kernel before passing the structure to the userland via
294 sysctl or routing socket. This means the KAME-specific embedded scope
295 id in sin6_addr.s6_addr[2] is always cleared in userland application.
296 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
297 __FreeBSD_version is bumped to 1000025.
300 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
301 This means that the world and kernel will be compiled with clang
302 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
303 and /usr/bin/cpp. To disable this behavior and revert to building
304 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
305 of current may need to bootstrap WITHOUT_CLANG first if the clang
306 build fails (its compatibility window doesn't extend to the 9 stable
310 The IPFIREWALL_FORWARD kernel option has been removed. Its
311 functionality now turned on by default.
314 The ZERO_COPY_SOCKET kernel option has been removed and
315 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
316 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
317 mechanism which is not safe and may result in kernel crashes.
318 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
319 driver supports disposeable external page sized mbuf storage.
320 Proper replacements for both zero-copy mechanisms are under
321 consideration and will eventually lead to complete removal
322 of the two kernel options.
325 The IPv4 network stack has been converted to network byte
326 order. The following modules need to be recompiled together
327 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
328 pf(4), ipfw(4), ng_ipfw(4), stf(4).
331 Support for non-MPSAFE filesystems was removed from VFS. The
332 VFS_VERSION was bumped, all filesystem modules shall be
336 All the non-MPSAFE filesystems have been disconnected from
337 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
338 portalfs, smbfs, xfs.
341 The interface cloning API and ABI has changed. The following
342 modules need to be recompiled together with kernel:
343 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
344 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
345 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
348 The sdhci driver was split in two parts: sdhci (generic SD Host
349 Controller logic) and sdhci_pci (actual hardware driver).
350 No kernel config modifications are required, but if you
351 load sdhc as a module you must switch to sdhci_pci instead.
354 Import the FUSE kernel and userland support into base system.
357 The GNU sort(1) program has been removed since the BSD-licensed
358 sort(1) has been the default for quite some time and no serious
359 problems have been reported. The corresponding WITH_GNU_SORT
363 The pfil(9) API/ABI for AF_INET family has been changed. Packet
364 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
368 The net80211(4) ABI has been changed to allow for improved driver
369 PS-POLL and power-save support. All wireless drivers need to be
370 recompiled to work with the new kernel.
373 The random(4) support for the VIA hardware random number
374 generator (`PADLOCK') is no longer enabled unconditionally.
375 Add the padlock_rng device in the custom kernel config if
376 needed. The GENERIC kernels on i386 and amd64 do include the
377 device, so the change only affects the custom kernel
381 The pf(4) packet filter ABI has been changed. pfctl(8) and
382 snmp_pf module need to be recompiled to work with new kernel.
385 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
386 to -HEAD. Pools that have empty_bpobj in active state can not be
387 imported read-write with ZFS implementations that do not support
388 this feature. For more information read the zpool-features(5)
392 The sparc64 ZFS loader has been changed to no longer try to auto-
393 detect ZFS providers based on diskN aliases but now requires these
394 to be explicitly listed in the OFW boot-device environment variable.
397 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
398 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
399 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
402 The following sysctls and tunables have been renamed for consistency
403 with other variables:
404 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
405 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
408 The sort utility has been replaced with BSD sort. For now, GNU sort
409 is also available as "gnusort" or the default can be set back to
410 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
411 installed as "bsdsort".
414 A new version of ZFS (pool version 5000) has been merged to -HEAD.
415 Starting with this version the old system of ZFS pool versioning
416 is superseded by "feature flags". This concept enables forward
417 compatibility against certain future changes in functionality of ZFS
418 pools. The first read-only compatible "feature flag" for ZFS pools
419 is named "com.delphix:async_destroy". For more information
420 read the new zpool-features(5) manual page.
421 Please refer to the "ZFS notes" section of this file for information
422 on upgrading boot ZFS pools.
425 The malloc(3) implementation embedded in libc now uses sources imported
426 as contrib/jemalloc. The most disruptive API change is to
427 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
428 delete it prior to installworld, and optionally re-create it using the
429 new format after rebooting. See malloc.conf(5) for details
430 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
434 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
435 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
436 now spelled mips. This is to aid compatibility with third-party
437 software that expects this naming scheme in uname(3). Little-endian
438 settings are unchanged. If you are updating a big-endian mips64 machine
439 from before this change, you may need to set MACHINE_ARCH=mips64 in
440 your environment before the new build system will recognize your machine.
443 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
447 Now unix domain sockets behave "as expected" on nullfs(5). Previously
448 nullfs(5) did not pass through all behaviours to the underlying layer,
449 as a result if we bound to a socket on the lower layer we could connect
450 only to the lower path; if we bound to the upper layer we could connect
451 only to the upper path. The new behavior is one can connect to both the
452 lower and the upper paths regardless what layer path one binds to.
455 The getifaddrs upgrade path broken with 20111215 has been restored.
456 If you have upgraded in between 20111215 and 20120209 you need to
457 recompile libc again with your kernel. You still need to recompile
458 world to be able to configure CARP but this restriction already
462 The set_rcvar() function has been removed from /etc/rc.subr. All
463 base and ports rc.d scripts have been updated, so if you have a
464 port installed with a script in /usr/local/etc/rc.d you can either
465 hand-edit the rcvar= line, or reinstall the port.
467 An easy way to handle the mass-update of /etc/rc.d:
468 rm /etc/rc.d/* && mergemaster -i
471 panic(9) now stops other CPUs in the SMP systems, disables interrupts
472 on the current CPU and prevents other threads from running.
473 This behavior can be reverted using the kern.stop_scheduler_on_panic
475 The new behavior can be incompatible with kern.sync_on_panic.
478 The carp(4) facility has been changed significantly. Configuration
479 of the CARP protocol via ifconfig(8) has changed, as well as format
480 of CARP events submitted to devd(8) has changed. See manual pages
481 for more information. The arpbalance feature of carp(4) is currently
482 not supported anymore.
484 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
485 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
486 need to be recompiled.
489 The acpi_wmi(4) status device /dev/wmistat has been renamed to
493 The option VFS_ALLOW_NONMPSAFE option has been added in order to
494 explicitely support non-MPSAFE filesystems.
495 It is on by default for all supported platform at this present
499 The broken amd(4) driver has been replaced with esp(4) in the amd64,
500 i386 and pc98 GENERIC kernel configuration files.
503 sysinstall has been removed
506 The stable/9 branch created in subversion. This corresponds to the
507 RELENG_9 branch in CVS.
510 This commit modifies vfs_register() so that it uses a hash
511 calculation to set vfc_typenum, which is enabled by default.
512 The first time a system is booted after this change, the
513 vfc_typenum values will change for all file systems. The
514 main effect of this is a change to the NFS server file handles
515 for file systems that use vfc_typenum in their fsid, such as ZFS.
516 It will, however, prevent vfc_typenum from changing when file
517 systems are loaded in a different order for subsequent reboots.
518 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
519 until you are ready to remount all NFS clients after a reboot.
522 Bump the shared library version numbers for libraries that
523 do not use symbol versioning, have changed the ABI compared
524 to stable/8 and which shared library version was not bumped.
525 Done as part of 9.0-RELEASE cycle.
528 During the merge of Capsicum features, the fget(9) KPI was modified.
529 This may require the rebuilding of out-of-tree device drivers --
530 issues have been reported specifically with the nVidia device driver.
531 __FreeBSD_version is bumped to 900041.
533 Also, there is a period between 20110811 and 20110814 where the
534 special devices /dev/{stdin,stdout,stderr} did not work correctly.
535 Building world from a kernel during that window may not work.
538 The packet filter (pf) code has been updated to OpenBSD 4.5.
539 You need to update userland tools to be in sync with kernel.
540 This update breaks backward compatibility with earlier pfsync(4)
541 versions. Care must be taken when updating redundant firewall setups.
544 The following sysctls and tunables are retired on x86 platforms:
546 machdep.hlt_logical_cpus
547 The following sysctl is retired:
548 machdep.hyperthreading_allowed
549 The sysctls were supposed to provide a way to dynamically offline and
550 online selected CPUs on x86 platforms, but the implementation has not
551 been reliable especially with SCHED_ULE scheduler.
552 machdep.hyperthreading_allowed tunable is still available to ignore
553 hyperthreading CPUs at OS level.
554 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
555 where X is an APIC ID of a CPU. Be advised, though, that disabling
556 CPUs in non-uniform fashion will result in non-uniform topology and
557 may lead to sub-optimal system performance with SCHED_ULE, which is
561 cpumask_t type is retired and cpuset_t is used in order to describe
565 Changes to ifconfig(8) for dynamic address family detection mandate
566 that you are running a kernel of 20110525 or later. Make sure to
567 follow the update procedure to boot a new kernel before installing
571 Support for sun4v architecture is officially dropped
574 Several KPI breaking changes have been committed to the mii(4) layer,
575 the PHY drivers and consequently some Ethernet drivers using mii(4).
576 This means that miibus.ko and the modules of the affected Ethernet
577 drivers need to be recompiled.
579 Note to kernel developers: Given that the OUI bit reversion problem
580 was fixed as part of these changes all mii(4) commits related to OUIs,
581 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
582 handling, no longer can be merged verbatim to stable/8 and previous
586 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
587 into their kernel configurations along with 'device pci'.
590 The default NFS client is now the new NFS client, so fstype "newnfs"
591 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
592 Although mounts via fstype "nfs" will usually work without userland
593 changes, it is recommended that the mount(8) and mount_nfs(8)
594 commands be rebuilt from sources and that a link to mount_nfs called
595 mount_oldnfs be created. The new client is compiled into the
596 kernel with "options NFSCL" and this is needed for diskless root
597 file systems. The GENERIC kernel configs have been changed to use
598 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
599 To use the regular/old client, you can "mount -t oldnfs ...". For
600 a diskless root file system, you must also include a line like:
602 vfs.root.mountfrom="oldnfs:"
604 in the boot/loader.conf on the root fs on the NFS server to make
605 a diskless root fs use the old client.
608 The GENERIC kernels for all architectures now default to the new
609 CAM-based ATA stack. It means that all legacy ATA drivers were
610 removed and replaced by respective CAM drivers. If you are using
611 ATA device names in /etc/fstab or other places, make sure to update
612 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
613 where 'Y's are the sequential numbers starting from zero for each type
614 in order of detection, unless configured otherwise with tunables,
615 see cam(4)). There will be symbolic links created in /dev/ to map
616 old adX devices to the respective adaY. They should provide basic
617 compatibility for file systems mounting in most cases, but they do
618 not support old user-level APIs and do not have respective providers
619 in GEOM. Consider using updated management tools with new device names.
621 It is possible to load devices ahci, ata, siis and mvs as modules,
622 but option ATA_CAM should remain in kernel configuration to make ata
623 module work as CAM driver supporting legacy ATA controllers. Device ata
624 still can be used in modular fashion (atacore + ...). Modules atadisk
625 and atapi* are not used and won't affect operation in ATA_CAM mode.
626 Note that to use CAM-based ATA kernel should include CAM devices
627 scbus, pass, da (or explicitly ada), cd and optionally others. All of
628 them are parts of the cam module.
630 ataraid(4) functionality is now supported by the RAID GEOM class.
631 To use it you can load geom_raid kernel module and use graid(8) tool
632 for management. Instead of /dev/arX device names, use /dev/raid/rX.
634 No kernel config options or code have been removed, so if a problem
635 arises, please report it and optionally revert to the old ATA stack.
636 In order to do it you can remove from the kernel config:
641 , and instead add back:
642 device atadisk # ATA disk drives
643 device ataraid # ATA RAID drives
644 device atapicd # ATAPI CDROM drives
645 device atapifd # ATAPI floppy drives
646 device atapist # ATAPI tape drives
649 The default NFS server has been changed to the new server, which
650 was referred to as the experimental server. If you need to switch
651 back to the old NFS server, you must now put the "-o" option on
652 both the mountd and nfsd commands. This can be done using the
653 mountd_flags and nfs_server_flags rc.conf variables until an
654 update to the rc scripts is committed, which is coming soon.
657 The GNU Objective-C runtime library (libobjc), and other Objective-C
658 related components have been removed from the base system. If you
659 require an Objective-C library, please use one of the available ports.
662 ath(4) has been split into bus- and device- modules. if_ath contains
663 the HAL, the TX rate control and the network device code. if_ath_pci
664 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
665 contains the AHB glue. Users need to load both if_ath_pci and if_ath
666 in order to use ath on everything else.
668 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
669 need to load if_ath and if_ath_pci for ath(4) operation.
672 As part of the replacement of sysinstall, the process of building
673 release media has changed significantly. For details, please re-read
674 release(7), which has been updated to reflect the new build process.
677 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
678 is the last available version under GPLv2. It brings a number of new
679 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
680 4.1 and SSE 4.2), better support for powerpc64, a number of new
681 directives, and lots of other small improvements. See the ChangeLog
682 file in contrib/binutils for the full details.
685 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
686 compliant, and will now use half of hash for authentication.
687 This will break interoperability with all stacks (including all
688 actual FreeBSD versions) who implement
689 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
691 The only workaround with such peers is to use another HMAC
692 algorithm for IPsec ("phase 2") authentication.
695 Remove the uio_yield prototype and symbol. This function has
696 been misnamed since it was introduced and should not be
697 globally exposed with this name. The equivalent functionality
698 is now available using kern_yield(curthread->td_user_pri).
699 The function remains undocumented.
702 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
703 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
704 for scalar sysctls is defined but disabled. Code that needs
705 UQUAD to pass the type checking that must compile on older
706 systems where the define is not present can check against
707 __FreeBSD_version >= 900030.
709 The system dialog(1) has been replaced with a new version previously
710 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
711 with the previous version, but the libdialog associated with it has
712 a largely incompatible API. As such, the original version of libdialog
713 will be kept temporarily as libodialog, until its base system consumers
714 are replaced or updated. Bump __FreeBSD_version to 900030.
717 If you are trying to run make universe on a -stable system, and you get
718 the following warning:
719 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
720 unknown. config(8) likely too old."
721 or something similar to it, then you must upgrade your -stable system
722 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
723 stable/8) or build the config from the latest stable/8 branch and
724 install it on your system.
726 Prior to this date, building a current universe on 8-stable system from
727 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
728 error in the first kernel build phase. A new config on those old
729 systems will fix that problem for older versions of -current.
732 The TCP stack has been modified to allow Khelp modules to interact with
733 it via helper hook points and store per-connection data in the TCP
734 control block. Bump __FreeBSD_version to 900029. User space tools that
735 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
739 Generic IEEE 802.3 annex 31B full duplex flow control support has been
740 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
741 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
742 to take advantage of it instead of using custom implementations. This
743 means that these drivers now no longer unconditionally advertise
744 support for flow control but only do so if flow control is a selected
745 media option. This was implemented in the generic support that way in
746 order to allow flow control to be switched on and off via ifconfig(8)
747 with the PHY specific default to typically off in order to protect
748 from unwanted effects. Consequently, if you used flow control with
749 one of the above mentioned drivers you now need to explicitly enable
751 ifconfig bge0 media auto mediaopt flowcontrol
753 Along with the above mentioned changes generic support for setting
754 1000baseT master mode also has been added and brgphy(4), ciphy(4),
755 e1000phy(4) as well as ip1000phy(4) have been converted to take
756 advantage of it. This means that these drivers now no longer take the
757 link0 parameter for selecting master mode but the master media option
758 has to be used instead, for example like in the following:
759 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
761 Selection of master mode now is also available with all other PHY
762 drivers supporting 1000baseT.
765 The TCP stack has received a significant update to add support for
766 modularised congestion control and generally improve the clarity of
767 congestion control decisions. Bump __FreeBSD_version to 900025. User
768 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
769 sockstat) need to be recompiled.
772 The man(1) utility has been replaced by a new version that no longer
773 uses /etc/manpath.config. Please consult man.conf(5) for how to
774 migrate local entries to the new format.
777 The copyright strings printed by login(1) and sshd(8) at the time of a
778 new connection have been removed to follow other operating systems and
782 A workaround for a fixed ld bug has been removed in kernel code,
783 so make sure that your system ld is built from sources after
784 revision 210245 from 2010-07-19 (r211583 if building head kernel
785 on stable/8, r211584 for stable/7; both from 2010-08-21).
786 A symptom of incorrect ld version is different addresses for
787 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
790 The $ipv6_prefer variable in rc.conf(5) has been split into
791 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
793 The $ip6addrctl_policy is a variable to choose a pre-defined
794 address selection policy set by ip6addrctl(8). A value
795 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
798 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
799 flag (see an entry of 20090926) is set on an interface with no
800 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
801 security reason. If you want IPv6 link-local address on all
802 interfaces by default, set this to "YES".
804 The old ipv6_prefer="YES" is equivalent to
805 ipv6_activate_all_interfaces="YES" and
806 ip6addrctl_policy="ipv6_prefer".
809 DTrace has grown support for userland tracing. Due to this, DTrace is
810 now i386 and amd64 only.
811 dtruss(1) is now installed by default on those systems and a new
812 kernel module is needed for userland tracing: fasttrap.
813 No changes to your kernel config file are necessary to enable
814 userland tracing, but you might consider adding 'STRIP=' and
815 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
816 to have informative userland stack traces in DTrace (ustack).
819 The acpi_aiboost(4) driver has been removed in favor of the new
820 aibs(4) driver. You should update your kernel configuration file.
823 BSD grep has been imported to the base system and it is built by
824 default. It is completely BSD licensed, highly GNU-compatible, uses
825 less memory than its GNU counterpart and has a small codebase.
826 However, it is slower than its GNU counterpart, which is mostly
827 noticeable for larger searches, for smaller ones it is measurable
828 but not significant. The reason is complex, the most important factor
829 is that we lack a modern and efficient regex library and GNU
830 overcomes this by optimizing the searches internally. Future work
831 on improving the regex performance is planned, for the meantime,
832 users that need better performance, can build GNU grep instead by
833 setting the WITH_GNU_GREP knob.
836 Due to the import of powerpc64 support, all existing powerpc kernel
837 configuration files must be updated with a machine directive like this:
838 machine powerpc powerpc
840 In addition, an updated config(8) is required to build powerpc kernels
844 A new version of ZFS (version 15) has been merged to -HEAD.
845 This version uses a python library for the following subcommands:
846 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
847 For full functionality of these commands the following port must
848 be installed: sysutils/py-zfs
851 'vm_page's are now hashed by physical address to an array of mutexes.
852 Currently this is only used to serialize access to hold_count. Over
853 time the page queue mutex will be peeled away. This changes the size
854 of pmap on every architecture. And requires all callers of vm_page_hold
855 and vm_page_unhold to be updated.
858 WITH_CTF can now be specified in src.conf (not recommended, there
859 are some problems with static executables), make.conf (would also
860 affect ports which do not use GNU make and do not override the
861 compile targets) or in the kernel config (via "makeoptions
863 When WITH_CTF was specified there before this was silently ignored,
864 so make sure that WITH_CTF is not used in places which could lead
865 to unwanted behavior.
868 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
869 to allow 32-bit compatibility on non-x86 platforms. All kernel
870 configurations on amd64 and ia64 platforms using these options must
871 be modified accordingly.
874 The utmp user accounting database has been replaced with utmpx,
875 the user accounting interface standardized by POSIX.
876 Unfortunately the semantics of utmp and utmpx don't match,
877 making it practically impossible to support both interfaces.
878 The user accounting database is used by tools like finger(1),
879 last(1), talk(1), w(1) and ac(8).
881 All applications in the base system use utmpx. This means only
882 local binaries (e.g. from the ports tree) may still use these
883 utmp database files. These applications must be rebuilt to make
886 After the system has been upgraded, it is safe to remove the old
887 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
888 assuming their contents is of no importance anymore. Old wtmp
889 databases can only be used by last(1) and ac(8) after they have
890 been converted to the new format using wtmpcvt(1).
893 Introduce the kernel thread "deadlock resolver" (which can be enabled
894 via the DEADLKRES option, see NOTES for more details) and the
895 sleepq_type() function for sleepqueues.
898 The rc.firewall and rc.firewall6 were unified, and
899 rc.firewall6 and rc.d/ip6fw were removed.
900 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
901 variables are obsoleted. Instead, the following new rc
902 variables are added to rc.d/ipfw:
904 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
905 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
906 firewall_simple_onet_ipv6, firewall_trusted_ipv6
908 The meanings correspond to the relevant IPv4 variables.
914 The default terminal emulation for syscons(4) has been changed
915 from cons25 to xterm on all platforms except pc98. This means
916 that the /etc/ttys file needs to be updated to ensure correct
917 operation of applications on the console.
919 The terminal emulation style can be toggled per window by using
920 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
921 options can be used to change the compile-time default back to
924 To prevent graphical artifacts, make sure the TERM environment
925 variable is set to match the terminal emulation that is being
926 performed by syscons(4).
929 The layout of the structure ieee80211req_scan_result has changed.
930 Applications that require wireless scan results (e.g. ifconfig(8))
931 from net80211 need to be recompiled.
933 Applications such as wpa_supplicant(8) may require a full world
934 build without using NO_CLEAN in order to get synchronized with the
938 The iwn(4) driver has been updated to support the 5000 and 5150 series.
939 There's one kernel module for each firmware. Adding "device iwnfw"
940 to the kernel configuration file means including all three firmware
941 images inside the kernel. If you want to include just the one for
942 your wireless card, use the devices iwn4965fw, iwn5000fw or
946 The rc.d/network_ipv6, IPv6 configuration script has been integrated
947 into rc.d/netif. The changes are the following:
949 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
950 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
951 Note that both variables need the "inet6" keyword at the head.
953 Do not set $ipv6_network_interfaces manually if you do not
954 understand what you are doing. It is not needed in most cases.
956 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
959 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
960 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
962 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
963 all configured interfaces have "inet6 accept_rtadv" in the
964 $ifconfig_IF_ipv6. These are for backward compatibility.
966 3. A new variable $ipv6_prefer has been added. If NO, IPv6
967 functionality of interfaces with no corresponding
968 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
969 and the default address selection policy of ip6addrctl(8)
970 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
971 Note that if you want to configure IPv6 functionality on the
972 disabled interfaces after boot, first you need to clear the flag by
973 using ifconfig(8) like:
975 ifconfig em0 inet6 -ifdisabled
977 If YES, the default address selection policy is set as
980 The default value of $ipv6_prefer is NO.
982 4. If your system need to receive Router Advertisement messages,
983 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
984 scripts automatically invoke rtsol(8) when the interface becomes
985 UP. The Router Advertisement messages are used for SLAAC
986 (State-Less Address AutoConfiguration).
989 802.11s D3.03 support was committed. This is incompatible with the
990 previous code, which was based on D3.0.
993 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
994 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
995 control whether accepting Router Advertisement messages or not.
996 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
997 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
998 The ifconfig(8) utility now supports these flags.
1001 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1002 mount(8) and -a option for df(1) to see them.
1005 The old tunable hw.bus.devctl_disable has been superseded by
1006 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1007 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1011 Remove the option STOP_NMI. The default action is now to use NMI only
1012 for KDB via the newly introduced function stop_cpus_hard() and
1013 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1016 The stable/8 branch created in subversion. This corresponds to the
1017 RELENG_8 branch in CVS.
1020 Bump the shared library version numbers for all libraries that do not
1021 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1022 __FreeBSD_version to 800105.
1025 Due to changes in the implementation of virtual network stack support,
1026 all network-related kernel modules must be recompiled. As this change
1027 breaks the ABI, bump __FreeBSD_version to 800104.
1030 The TOE interface to the TCP syncache has been modified to remove
1031 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1032 The cxgb driver is the only TOE consumer affected by this change, and
1033 needs to be recompiled along with the kernel. As this change breaks
1034 the ABI, bump __FreeBSD_version to 800103.
1037 Padding has been added to struct tcpcb, sackhint and tcpstat in
1038 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1039 maintaining the ABI. However, this change breaks the ABI, so bump
1040 __FreeBSD_version to 800102. User space tools that rely on the size of
1041 any of these structs (e.g. sockstat) need to be recompiled.
1044 The NFS_LEGACYRPC option has been removed along with the old kernel
1045 RPC implementation that this option selected. Kernel configurations
1046 may need to be adjusted.
1049 The network interface device nodes at /dev/net/<interface> have been
1050 removed. All ioctl operations can be performed the normal way using
1051 routing sockets. The kqueue functionality can generally be replaced
1052 with routing sockets.
1055 The documentation from the FreeBSD Documentation Project (Handbook,
1056 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1057 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1060 The ABI of various structures related to the SYSV IPC API have been
1061 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1062 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1066 Layout of struct vnet has changed as routing related variables were
1067 moved to their own Vimage module. Modules need to be recompiled. Bump
1068 __FreeBSD_version to 800099.
1071 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1072 respectively. As long as no more than 16 groups per process are used,
1073 no changes should be visible. When more than 16 groups are used, old
1074 binaries may fail if they call getgroups() or getgrouplist() with
1075 statically sized storage. Recompiling will work around this, but
1076 applications should be modified to use dynamically allocated storage
1077 for group arrays as POSIX.1-2008 does not cap an implementation's
1078 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1080 NFS and portalfs mounts may also be affected as the list of groups is
1081 truncated to 16. Users of NFS who use more than 16 groups, should
1082 take care that negative group permissions are not used on the exported
1083 file systems as they will not be reliable unless a GSSAPI based
1084 authentication method is used.
1087 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1088 option compiles in the support for adaptive spinning for lockmgrs
1089 which want to enable it. The lockinit() function now accepts the flag
1090 LK_ADAPTIVE in order to make the lock object subject to adaptive
1091 spinning when both held in write and read mode.
1094 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1095 changed. User applications that use this ioctl need to be rebuilt.
1098 The layout of struct thread has changed. Kernel and modules need to
1102 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1103 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1106 window(1) has been removed from the base system. It can now be
1107 installed from ports. The port is called misc/window.
1110 The way we are storing and accessing `routing table' entries has
1111 changed. Programs reading the FIB, like netstat, need to be
1115 A new netisr implementation has been added for FreeBSD 8. Network
1116 file system modules, such as igmp, ipdivert, and others, should be
1118 Bump __FreeBSD_version to 800096.
1121 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1125 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1126 Bump __FreeBSD_version to 800094.
1129 Add mnt_xflag field to 'struct mount'. File system modules need to be
1131 Bump __FreeBSD_version to 800093.
1134 The compiling option ADAPTIVE_SX has been retired while it has been
1135 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1136 The KPI for sx_init_flags() changes as accepting flags:
1137 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1138 been introduced in order to handle the reversed logic.
1139 Bump __FreeBSD_version to 800092.
1142 Add support for hierarchical jails. Remove global securelevel.
1143 Bump __FreeBSD_version to 800091.
1146 The layout of struct vnet_net has changed, therefore modules
1148 Bump __FreeBSD_version to 800090.
1151 The newly imported zic(8) produces a new format in the output. Please
1152 run tzsetup(8) to install the newly created data to /etc/localtime.
1155 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1156 hw.usb.* and is now consistent again with previous releases.
1159 802.11 monitor mode support was revised and driver api's were changed.
1160 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1161 of DLT_IEEE802_11. No user-visible data structures were changed but
1162 applications that use DLT_IEEE802_11 may require changes.
1163 Bump __FreeBSD_version to 800088.
1166 The layout of the following structs has changed: sysctl_oid,
1167 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1168 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1169 panics may be experienced. World rebuild is required for
1170 correctly checking networking state from userland.
1171 Bump __FreeBSD_version to 800085.
1174 MLDv2 and Source-Specific Multicast (SSM) have been merged
1175 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1176 The implementation of SSM within FreeBSD's IPv6 stack closely
1177 follows the IPv4 implementation.
1179 For kernel developers:
1181 * The most important changes are that the ip6_output() and
1182 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1183 and this lock has been downgraded to a non-recursive mutex.
1185 * As with the changes to the IPv4 stack to support SSM, filtering
1186 of inbound multicast traffic must now be performed by transport
1187 protocols within the IPv6 stack. This does not apply to TCP and
1188 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1190 * The KPIs used by IPv6 multicast are similar to those used by
1191 the IPv4 stack, with the following differences:
1192 * im6o_mc_filter() is analogous to imo_multicast_filter().
1193 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1194 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1195 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1196 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1197 for MLDv1 have an additional 'timer' argument which is used to
1198 jitter the initial membership report for the solicited-node
1199 multicast membership on-link.
1200 * This is not strictly needed for MLDv2, which already jitters
1201 its report transmissions. However, the 'timer' argument is
1202 preserved in case MLDv1 is active on the interface.
1204 * The KAME linked-list based IPv6 membership implementation has
1205 been refactored to use a vector similar to that used by the IPv4
1207 Code which maintains a list of its own multicast memberships
1208 internally, e.g. carp, has been updated to reflect the new
1211 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1212 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1213 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1214 implementation constraint which needs to be addressed in HEAD.
1216 For application developers:
1218 * The changes are broadly similar to those made for the IPv4
1221 * The use of IPv4 and IPv6 multicast socket options on the same
1222 socket, using mapped addresses, HAS NOT been tested or supported.
1224 * There are a number of issues with the implementation of various
1225 IPv6 multicast APIs which need to be resolved in the API surface
1226 before the implementation is fully compatible with KAME userland
1227 use, and these are mostly to do with interface index treatment.
1229 * The literature available discusses the use of either the delta / ASM
1230 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1231 using setsourcefilter(3)/getsourcefilter(3). For more information
1232 please refer to RFC 3768, 'Socket Interface Extensions for
1233 Multicast Source Filters'.
1235 * Applications which use the published RFC 3678 APIs should be fine.
1237 For systems administrators:
1239 * The mtest(8) utility has been refactored to support IPv6, in
1240 addition to IPv4. Interface addresses are no longer accepted
1241 as arguments, their names must be used instead. The utility
1242 will map the interface name to its first IPv4 address as
1243 returned by getifaddrs(3).
1245 * The ifmcstat(8) utility has also been updated to print the MLDv2
1246 endpoint state and source filter lists via sysctl(3).
1248 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1249 loopback of IPv6 multicast datagrams by default; it defaults to 1
1250 to preserve the existing behaviour. Disabling multicast loopback is
1251 recommended for optimal system performance.
1253 * The IPv6 MROUTING code has been changed to examine this sysctl
1254 instead of attempting to perform a group lookup before looping
1255 back forwarded datagrams.
1257 Bump __FreeBSD_version to 800084.
1260 Implement low-level Bluetooth HCI API.
1261 Bump __FreeBSD_version to 800083.
1264 The layout of struct malloc_type, used by modules to register new
1265 memory allocation types, has changed. Most modules will need to
1266 be rebuilt or panics may be experienced.
1267 Bump __FreeBSD_version to 800081.
1270 Anticipate overflowing inp_flags - add inp_flags2.
1271 This changes most offsets in inpcb, so checking v4 connection
1272 state will require a world rebuild.
1273 Bump __FreeBSD_version to 800080.
1276 Add an llentry to struct route and struct route_in6. Modules
1277 embedding a struct route will need to be recompiled.
1278 Bump __FreeBSD_version to 800079.
1281 The size of rt_metrics_lite and by extension rtentry has changed.
1282 Networking administration apps will need to be recompiled.
1283 The route command now supports show as an alias for get, weighting
1284 of routes, sticky and nostick flags to alter the behavior of stateful
1286 Bump __FreeBSD_version to 800078.
1289 Do not use Giant for kbdmux(4) locking. This is wrong and
1290 apparently causing more problems than it solves. This will
1291 re-open the issue where interrupt handlers may race with
1292 kbdmux(4) in polling mode. Typical symptoms include (but
1293 not limited to) duplicated and/or missing characters when
1294 low level console functions (such as gets) are used while
1295 interrupts are enabled (for example geli password prompt,
1296 mountroot prompt etc.). Disabling kbdmux(4) may help.
1299 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1300 kernel modules referencing any of the above need to be recompiled.
1301 Bump __FreeBSD_version to 800075.
1304 GEOM_PART has become the default partition slicer for storage devices,
1305 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1306 introduces some changes:
1308 MSDOS/EBR: the devices created from MSDOS extended partition entries
1309 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1310 to devices with offset-based names. fstabs may need to be modified.
1312 BSD: the "geometry does not match label" warning is harmless in most
1313 cases but it points to problems in file system misalignment with
1314 disk geometry. The "c" partition is now implicit, covers the whole
1315 top-level drive and cannot be (mis)used by users.
1317 General: Kernel dumps are now not allowed to be written to devices
1318 whose partition types indicate they are meant to be used for file
1319 systems (or, in case of MSDOS partitions, as something else than
1322 Most of these changes date approximately from 200812.
1325 The uscanner(4) driver has been removed from the kernel. This follows
1326 Linux removing theirs in 2.6 and making libusb the default interface
1327 (supported by sane).
1330 The multicast forwarding code has been cleaned up. netstat(1)
1331 only relies on KVM now for printing bandwidth upcall meters.
1332 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1333 ip6_mroute_mod respectively. The config(5) options for statically
1334 compiling this code remain the same, i.e. 'options MROUTING'.
1337 Support for the IFF_NEEDSGIANT network interface flag has been
1338 removed, which means that non-MPSAFE network device drivers are no
1339 longer supported. In particular, if_ar, if_sr, and network device
1340 drivers from the old (legacy) USB stack can no longer be built or
1344 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1345 a bunch of new language catalog files have also been added.
1346 This means that some common libc messages are now localized and
1347 they depend on the LC_MESSAGES environmental variable.
1350 The k8temp(4) driver has been renamed to amdtemp(4) since
1351 support for Family 10 and Family 11 CPU families was added.
1354 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1355 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1357 For kernel developers, the most important changes are that the
1358 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1359 and this lock has been downgraded to a non-recursive mutex.
1361 Transport protocols (UDP, Raw IP) are now responsible for filtering
1362 inbound multicast traffic according to group membership and source
1363 filters. The imo_multicast_filter() KPI exists for this purpose.
1364 Transports which do not use multicast (SCTP, TCP) already reject
1365 multicast by default. Forwarding and receive performance may improve
1366 as a mutex acquisition is no longer needed in the ip_input()
1367 low-level input path. in_addmulti() and in_delmulti() are shimmed
1368 to new KPIs which exist to support SSM in-kernel.
1370 For application developers, it is recommended that loopback of
1371 multicast datagrams be disabled for best performance, as this
1372 will still cause the lock to be taken for each looped-back
1373 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1374 be tuned to 0 to disable loopback by default; it defaults to 1
1375 to preserve the existing behaviour.
1377 For systems administrators, to obtain best performance with
1378 multicast reception and multiple groups, it is always recommended
1379 that a card with a suitably precise hash filter is used. Hash
1380 collisions will still result in the lock being taken within the
1381 transport protocol input path to check group membership.
1383 If deploying FreeBSD in an environment with IGMP snooping switches,
1384 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1385 enabled; this forces 224.0.0.0/24 group membership to be announced
1388 The size of 'struct igmpstat' has changed; netstat needs to be
1389 recompiled to reflect this.
1390 Bump __FreeBSD_version to 800070.
1393 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1394 updated to use it. This requires a buildworld/installworld in order to
1395 update the library and dependencies (usbconfig, etc). Its advisable to
1396 rebuild all ports which uses libusb. More specific directions are given
1397 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1398 libusb are no longer required and can be removed.
1401 A workaround is committed to allow the creation of System V shared
1402 memory segment of size > 2 GB on the 64-bit architectures.
1403 Due to a limitation of the existing ABI, the shm_segsz member
1404 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1405 wrong for large segments. Note that limits must be explicitly
1406 raised to allow such segments to be created.
1409 The layout of struct ifnet has changed, requiring a rebuild of all
1410 network device driver modules.
1413 The /dev handling for the new USB stack has changed, a
1414 buildworld/installworld is required for libusb20.
1417 The new USB2 stack has now been permanently moved in and all kernel and
1418 module names reverted to their previous values (eg, usb, ehci, ohci,
1419 ums, ...). The old usb stack can be compiled in by prefixing the name
1420 with the letter 'o', the old usb modules have been removed.
1421 Updating entry 20090216 for xorg and 20090215 for libmap may still
1425 The rc.conf(5) option if_up_delay has been renamed to
1426 defaultroute_delay to better reflect its purpose. If you have
1427 customized this setting in /etc/rc.conf you need to update it to
1431 xorg 7.4 wants to configure its input devices via hald which does not
1432 yet work with USB2. If the keyboard/mouse does not work in xorg then
1434 Option "AllowEmptyInput" "off"
1435 to your ServerLayout section. This will cause X to use the configured
1436 kbd and mouse sections from your xorg.conf.
1439 The GENERIC kernels for all architectures now default to the new USB2
1440 stack. No kernel config options or code have been removed so if a
1441 problem arises please report it and optionally revert to the old USB
1442 stack. If you are loading USB kernel modules or have a custom kernel
1443 that includes GENERIC then ensure that usb names are also changed over,
1444 eg uftdi -> usb2_serial_ftdi.
1446 Older programs linked against the ports libusb 0.1 need to be
1447 redirected to the new stack's libusb20. /etc/libmap.conf can
1449 # Map old usb library to new one for usb2 stack
1450 libusb-0.1.so.8 libusb20.so.1
1453 All USB ethernet devices now attach as interfaces under the name ueN
1454 (eg. ue0). This is to provide a predictable name as vendors often
1455 change usb chipsets in a product without notice.
1458 The ichsmb(4) driver has been changed to require SMBus slave
1459 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1460 All of the other SMBus controller drivers require left-justified
1461 slave addresses, so this change makes all the drivers provide the
1465 INET6 statistics (struct ip6stat) was updated.
1466 netstat(1) needs to be recompiled.
1469 NTFS has been removed from GENERIC kernel on amd64 to match
1470 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1471 will load ntfs.ko module automatically when NTFS support is
1472 actually needed, unless ntfs.ko is not installed or security
1473 level prohibits loading kernel modules. If either is the case,
1474 "options NTFS" has to be added into kernel config.
1477 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1478 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1479 800061. User space tools that rely on the size of struct tcpcb in
1480 tcp_var.h (e.g. sockstat) need to be recompiled.
1483 ng_tty(4) module updated to match the new TTY subsystem.
1484 Due to API change, user-level applications must be updated.
1485 New API support added to mpd5 CVS and expected to be present
1486 in next mpd5.3 release.
1489 With __FreeBSD_version 800060 the makefs tool is part of
1490 the base system (it was a port).
1493 The afdata and ifnet locks have been changed from mutexes to
1494 rwlocks, network modules will need to be re-compiled.
1497 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1498 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1499 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1500 architecture and 40 bytes on 64-bit architecture. The userland
1501 applications "arp" and "ndp" have been updated accordingly.
1502 The output from "netstat -r" shows only routing entries and
1503 none of the L2 information.
1506 __FreeBSD_version 800057 marks the switchover from the
1507 binary ath hal to source code. Users must add the line:
1509 options AH_SUPPORT_AR5416
1511 to their kernel config files when specifying:
1515 The ath_hal module no longer exists; the code is now compiled
1516 together with the driver in the ath module. It is now
1517 possible to tailor chip support (i.e. reduce the set of chips
1518 and thereby the code size); consult ath_hal(4) for details.
1521 __FreeBSD_version 800054 adds memory barriers to
1522 <machine/atomic.h>, new interfaces to ifnet to facilitate
1523 multiple hardware transmit queues for cards that support
1524 them, and a lock-less ring-buffer implementation to
1525 enable drivers to more efficiently manage queueing of
1529 A new version of ZFS (version 13) has been merged to -HEAD.
1530 This version has zpool attribute "listsnapshots" off by
1531 default, which means "zfs list" does not show snapshots,
1532 and is the same as Solaris behavior.
1535 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1538 The uhci, ohci, ehci and slhci USB Host controller drivers have
1539 been put into separate modules. If you load the usb module
1540 separately through loader.conf you will need to load the
1541 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1542 controller add the following to loader.conf:
1548 The ABI used by the PMC toolset has changed. Please keep
1549 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1553 atapci kernel module now includes only generic PCI ATA
1554 driver. AHCI driver moved to ataahci kernel module.
1555 All vendor-specific code moved into separate kernel modules:
1556 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1557 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1558 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1559 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1562 The TTY subsystem of the kernel has been replaced by a new
1563 implementation, which provides better scalability and an
1564 improved driver model. Most common drivers have been migrated to
1565 the new TTY subsystem, while others have not. The following
1566 drivers have not yet been ported to the new TTY layer:
1569 cy, digi, rc, rp, sio
1575 ng_h4, ng_tty, ppp, sl, snp
1577 Adding these drivers to your kernel configuration file shall
1578 cause compilation to fail.
1581 ntpd has been upgraded to 4.2.4p5.
1584 OpenSSH has been upgraded to 5.1p1.
1586 For many years, FreeBSD's version of OpenSSH preferred DSA
1587 over RSA for host and user authentication keys. With this
1588 upgrade, we've switched to the vendor's default of RSA over
1589 DSA. This may cause upgraded clients to warn about unknown
1590 host keys even for previously known hosts. Users should
1591 follow the usual procedure for verifying host keys before
1592 accepting the RSA key.
1594 This can be circumvented by setting the "HostKeyAlgorithms"
1595 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1598 Please note that the sequence of keys offered for
1599 authentication has been changed as well. You may want to
1600 specify IdentityFile in a different order to revert this
1604 The sio(4) driver has been removed from the i386 and amd64
1605 kernel configuration files. This means uart(4) is now the
1606 default serial port driver on those platforms as well.
1608 To prevent collisions with the sio(4) driver, the uart(4) driver
1609 uses different names for its device nodes. This means the
1610 onboard serial port will now most likely be called "ttyu0"
1611 instead of "ttyd0". You may need to reconfigure applications to
1612 use the new device names.
1614 When using the serial port as a boot console, be sure to update
1615 /boot/device.hints and /etc/ttys before booting the new kernel.
1616 If you forget to do so, you can still manually specify the hints
1617 at the loader prompt:
1619 set hint.uart.0.at="isa"
1620 set hint.uart.0.port="0x3F8"
1621 set hint.uart.0.flags="0x10"
1622 set hint.uart.0.irq="4"
1626 The gpt(8) utility has been removed. Use gpart(8) to partition
1630 The version that Linuxulator emulates was changed from 2.4.2
1631 to 2.6.16. If you experience any problems with Linux binaries
1632 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1633 if it fixes the problem contact emulation mailing list.
1636 ISDN4BSD (I4B) was removed from the src tree. You may need to
1637 update a your kernel configuration and remove relevant entries.
1640 I have checked in code to support multiple routing tables.
1641 See the man pages setfib(1) and setfib(2).
1642 This is a hopefully backwards compatible version,
1643 but to make use of it you need to compile your kernel
1644 with options ROUTETABLES=2 (or more up to 16).
1647 The 802.11 wireless support was redone to enable multi-bss
1648 operation on devices that are capable. The underlying device
1649 is no longer used directly but instead wlanX devices are
1650 cloned with ifconfig. This requires changes to rc.conf files.
1651 For example, change:
1652 ifconfig_ath0="WPA DHCP"
1655 ifconfig_wlan0="WPA DHCP"
1656 see rc.conf(5) for more details. In addition, mergemaster of
1657 /etc/rc.d is highly recommended. Simultaneous update of userland
1658 and kernel wouldn't hurt either.
1660 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1661 modules were merged into the base wlan module. All references
1662 to these modules (e.g. in kernel config files) must be removed.
1665 psm(4) has gained write(2) support in native operation level.
1666 Arbitrary commands can be written to /dev/psm%d and status can
1667 be read back from it. Therefore, an application is responsible
1668 for status validation and error recovery. It is a no-op in
1669 other operation levels.
1672 Support for KSE threading has been removed from the kernel. To
1673 run legacy applications linked against KSE libmap.conf may
1674 be used. The following libmap.conf may be used to ensure
1675 compatibility with any prior release:
1677 libpthread.so.1 libthr.so.1
1678 libpthread.so.2 libthr.so.2
1679 libkse.so.3 libthr.so.3
1682 The layout of struct vmspace has changed. This affects libkvm
1683 and any executables that link against libkvm and use the
1684 kvm_getprocs() function. In particular, but not exclusively,
1685 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1686 The effects are minimal, but it's advisable to upgrade world
1690 The latest em driver no longer has support in it for the
1691 82575 adapter, this is now moved to the igb driver. The
1692 split was done to make new features that are incompatible
1693 with older hardware easier to do.
1696 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1697 likewise the kernel option is now GEOM_LINUX_LVM.
1700 The default NFS mount mode has changed from UDP to TCP for
1701 increased reliability. If you rely on (insecurely) NFS
1702 mounting across a firewall you may need to update your
1706 Belatedly note the addition of m_collapse for compacting
1710 The fts(3) structures have been changed to use adequate
1711 integer types for their members and so to be able to cope
1712 with huge file trees. The old fts(3) ABI is preserved
1713 through symbol versioning in libc, so third-party binaries
1714 using fts(3) should still work, although they will not take
1715 advantage of the extended types. At the same time, some
1716 third-party software might fail to build after this change
1717 due to unportable assumptions made in its source code about
1718 fts(3) structure members. Such software should be fixed
1719 by its vendor or, in the worst case, in the ports tree.
1720 FreeBSD_version 800015 marks this change for the unlikely
1721 case that a portable fix is impossible.
1724 To upgrade to -current after this date, you must be running
1725 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1726 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1729 The ADAPTIVE_GIANT kernel option has been retired because its
1730 functionality is the default now.
1733 The AT keyboard emulation of sunkbd(4) has been turned on
1734 by default. In order to make the special symbols of the Sun
1735 keyboards driven by sunkbd(4) work under X these now have
1736 to be configured the same way as Sun USB keyboards driven
1737 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1739 Option "XkbLayout" "us"
1740 Option "XkbRules" "xorg"
1741 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1744 It has been decided that it is desirable to provide ABI
1745 backwards compatibility to the FreeBSD 4/5/6 versions of the
1746 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1747 broken with the introduction of PCI domain support (see the
1748 20070930 entry). Unfortunately, this required the ABI of
1749 PCIOCGETCONF to be broken again in order to be able to
1750 provide backwards compatibility to the old version of that
1751 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1752 again. As for prominent ports this affects neither pciutils
1753 nor xorg-server this time, the hal port needs to be rebuilt
1757 The misnamed kthread_create() and friends have been renamed
1758 to kproc_create() etc. Many of the callers already
1759 used kproc_start()..
1760 I will return kthread_create() and friends in a while
1761 with implementations that actually create threads, not procs.
1762 Renaming corresponds with version 800002.
1771 Avoid using make -j when upgrading. While generally safe, there are
1772 sometimes problems using -j to upgrade. If your upgrade fails with
1773 -j, please try again without -j. From time to time in the past there
1774 have been problems using -j with buildworld and/or installworld. This
1775 is especially true when upgrading between "distant" versions (eg one
1776 that cross a major release boundary or several minor releases, or when
1777 several months have passed on the -current branch).
1779 Sometimes, obscure build problems are the result of environment
1780 poisoning. This can happen because the make utility reads its
1781 environment when searching for values for global variables. To run
1782 your build attempts in an "environmental clean room", prefix all make
1783 commands with 'env -i '. See the env(1) manual page for more details.
1785 When upgrading from one major version to another it is generally best
1786 to upgrade to the latest code in the currently installed branch first,
1787 then do an upgrade to the new branch. This is the best-tested upgrade
1788 path, and has the highest probability of being successful. Please try
1789 this approach before reporting problems with a major version upgrade.
1791 When upgrading a live system, having a root shell around before
1792 installing anything can help undo problems. Not having a root shell
1793 around can lead to problems if pam has changed too much from your
1794 starting point to allow continued authentication after the upgrade.
1798 When upgrading the boot ZFS pool to a new version, always follow
1801 1.) recompile and reinstall the ZFS boot loader and boot block
1802 (this is part of "make buildworld" and "make installworld")
1804 2.) update the ZFS boot block on your boot drive
1806 The following example updates the ZFS boot block on the first
1807 partition (freebsd-boot) of a GPT partitioned drive ad0:
1808 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1810 Non-boot pools do not need these updates.
1814 If you are updating from a prior version of FreeBSD (even one just
1815 a few days old), you should follow this procedure. It is the most
1816 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1818 make kernel-toolchain
1819 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1820 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1822 To test a kernel once
1823 ---------------------
1824 If you just want to boot a kernel once (because you are not sure
1825 if it works, or if you want to boot a known bad kernel to provide
1826 debugging information) run
1827 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1828 nextboot -k testkernel
1830 To just build a kernel when you know that it won't mess you up
1831 --------------------------------------------------------------
1832 This assumes you are already running a CURRENT system. Replace
1833 ${arch} with the architecture of your machine (e.g. "i386",
1834 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1836 cd src/sys/${arch}/conf
1837 config KERNEL_NAME_HERE
1838 cd ../compile/KERNEL_NAME_HERE
1843 If this fails, go to the "To build a kernel" section.
1845 To rebuild everything and install it on the current system.
1846 -----------------------------------------------------------
1847 # Note: sometimes if you are running current you gotta do more than
1848 # is listed here if you are upgrading from a really old current.
1850 <make sure you have good level 0 dumps>
1852 make kernel KERNCONF=YOUR_KERNEL_HERE
1854 <reboot in single user> [3]
1861 To cross-install current onto a separate partition
1862 --------------------------------------------------
1863 # In this approach we use a separate partition to hold
1864 # current's root, 'usr', and 'var' directories. A partition
1865 # holding "/", "/usr" and "/var" should be about 2GB in
1868 <make sure you have good level 0 dumps>
1871 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1872 <maybe newfs current's root partition>
1873 <mount current's root partition on directory ${CURRENT_ROOT}>
1874 make installworld DESTDIR=${CURRENT_ROOT}
1875 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1876 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1877 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1878 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1879 <reboot into current>
1880 <do a "native" rebuild/install as described in the previous section>
1881 <maybe install compatibility libraries from ports/misc/compat*>
1885 To upgrade in-place from stable to current
1886 ----------------------------------------------
1887 <make sure you have good level 0 dumps>
1889 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1891 <reboot in single user> [3]
1898 Make sure that you've read the UPDATING file to understand the
1899 tweaks to various things you need. At this point in the life
1900 cycle of current, things change often and you are on your own
1901 to cope. The defaults can also change, so please read ALL of
1902 the UPDATING entries.
1904 Also, if you are tracking -current, you must be subscribed to
1905 freebsd-current@freebsd.org. Make sure that before you update
1906 your sources that you have read and understood all the recent
1907 messages there. If in doubt, please track -stable which has
1908 much fewer pitfalls.
1910 [1] If you have third party modules, such as vmware, you
1911 should disable them at this point so they don't crash your
1914 [3] From the bootblocks, boot -s, and then do
1919 adjkerntz -i # if CMOS is wall time
1920 Also, when doing a major release upgrade, it is required that
1921 you boot into single user mode to do the installworld.
1923 [4] Note: This step is non-optional. Failure to do this step
1924 can result in a significant reduction in the functionality of the
1925 system. Attempting to do it by hand is not recommended and those
1926 that pursue this avenue should read this file carefully, as well
1927 as the archives of freebsd-current and freebsd-hackers mailing lists
1928 for potential gotchas. The -U option is also useful to consider.
1929 See mergemaster(8) for more information.
1931 [5] Usually this step is a noop. However, from time to time
1932 you may need to do this if you get unknown user in the following
1933 step. It never hurts to do it all the time. You may need to
1934 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1935 install) after the buildworld before this step if you last updated
1936 from current before 20130425 or from -stable before 20130430.
1938 [6] This only deletes old files and directories. Old libraries
1939 can be deleted by "make delete-old-libs", but you have to make
1940 sure that no program is using those libraries anymore.
1942 [8] In order to have a kernel that can run the 4.x binaries needed to
1943 do an installworld, you must include the COMPAT_FREEBSD4 option in
1944 your kernel. Failure to do so may leave you with a system that is
1945 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1946 required to run the 5.x binaries on more recent kernels. And so on
1947 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1949 Make sure that you merge any new devices from GENERIC since the
1950 last time you updated your kernel config file.
1952 [9] When checking out sources, you must include the -P flag to have
1953 cvs prune empty directories.
1955 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1956 "?=" instead of the "=" assignment operator, so that buildworld can
1957 override the CPUTYPE if it needs to.
1959 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1960 not on the command line, or in /etc/make.conf. buildworld will
1961 warn if it is improperly defined.
1964 This file contains a list, in reverse chronological order, of major
1965 breakages in tracking -current. It is not guaranteed to be a complete
1966 list of such breakages, and only contains entries since October 10, 2007.
1967 If you need to see UPDATING entries from before that date, you will need
1968 to fetch an UPDATING file from an older FreeBSD release.
1970 Copyright information:
1972 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1974 Redistribution, publication, translation and use, with or without
1975 modification, in full or in part, in any form or format of this
1976 document are permitted without further permission from the author.
1978 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1979 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1980 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1981 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1982 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1983 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1984 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1985 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1986 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1987 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1988 POSSIBILITY OF SUCH DAMAGE.
1990 Contact Warner Losh if you have any questions about your use of