CTM_BEGIN 2.0 src-10 410 20140827110543Z .
CTMFS .ctm_status 1004 1004 644 7053dd70b144b9f158287d9f84f57dac d79d9b8d759d8baa45d6cace06ed8db4 11
src-10 410

CTMFN release/arm/release.sh 1004 1004 755 55f4da46ca2cc40678155c7c5573c31c 848fe4c6005caff13cd08bbf0d2d4bdb 396
d30 1
a30 1
# $FreeBSD: stable/10/release/arm/release.sh 270688 2014-08-27 00:50:51Z gjb $
a94 8
	# Fix broken ports that use kern.osreldate.
	OSVERSION=$(chroot ${CHROOTDIR} /usr/bin/uname -U)
	export OSVERSION
	REVISION=$(chroot ${CHROOTDIR} make -C /usr/src/release -V REVISION)
	BRANCH=$(chroot ${CHROOTDIR} make -C /usr/src/release -V BRANCH)
	UNAME_r=${REVISION}-${BRANCH}
	export UNAME_r


CTMFN release/doc/en_US.ISO8859-1/errata/article.xml 1004 1004 644 0f672e3a010b229c3e155659fe58e39e ed1acd87dabe96bc2d7ff57d9b7c0a7e 2327
d3 1
a3 1
  "http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd" [
d5 1
a5 1
  "http://www.FreeBSD.org/release/XML/release.ent">
d10 2
a11 2
  xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">

d17 1
a17 1
    <pubdate>$FreeBSD: stable/10/release/doc/en_US.ISO8859-1/errata/article.xml 270686 2014-08-27 00:07:33Z gjb $</pubdate>
d22 1
a22 2
      <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
	Project</holder>
d34 7
a40 7
	containing significant information discovered after the
	release or too late in the release cycle to be otherwise
	included in the release documentation.  This information
	includes security advisories, as well as news relating to the
	software or documentation that could affect its operation or
	usability.  An up-to-date version of this document should
	always be consulted before installing this version of
d43 2
a44 2
      <para>This errata document for &os; &release.prev; will be
	maintained until the release of &os; &release.next;.</para>
d51 5
a55 5
    <para>This errata document contains <quote>late-breaking
	news</quote> about &os; &release.prev; Before installing this
      version, it is important to consult this document to learn about
      any post-release discoveries or problems that may already have
      been found and fixed.</para>
d61 5
a65 4
	errata</quote> for this release.  These other copies of the
      errata are located at <link
	xlink:href="http://www.FreeBSD.org/releases/" />, plus any
      sites which keep up-to-date mirrors of this location.</para>
d71 3
a73 3
    <para>For a list of all &os; CERT security advisories, see <link
	xlink:href="http://www.FreeBSD.org/security/"/> or <link
      xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/"/>.</para>
d243 4
a246 4
	  works as a workaround.  To disable it, choose
	  <literal>Escape to loader prompt</literal> in the boot menu
	  and enter the following lines from &man.loader.8; prompt,
	  after an <literal>OK</literal>:</para>
d252 2
a253 2
	  <filename>/boot/loader.conf</filename> after a boot.  It
	  disables unmapped I/O at every boot:</para>
d298 1
a298 2
	<para>This bug has been fixed on &os;
	  &release.current;.</para>
d330 1
a330 1
	  in &os;-CURRENT and &os; &release.current;.</para>
d336 1
a336 1
	  the system to hang, or may cause the system to panic.  This

CTMFN release/doc/en_US.ISO8859-1/hardware/article.xml 1004 1004 644 91d5251a490d198659c1190294a17d42 b667bcc97159862d3f62a7cad918aadf 5135
d3 1
a3 1
  "../../../share/xml/freebsd50.dtd" [
d9 3
a11 4
<article xmlns="http://docbook.org/ns/docbook"
  xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
  <info>
    <title>&os; &release.current; Hardware Notes</title>
d15 1
a15 1
    <pubdate>$FreeBSD: stable/10/release/doc/en_US.ISO8859-1/hardware/article.xml 270682 2014-08-26 23:45:26Z gjb $</pubdate>
d33 1
a33 2
      <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
	Project</holder>
d46 1
d100 2
a101 2
	  <para>The single-core &intel; &xeon; processors
	    <quote>Nocona</quote>, <quote>Irwindale</quote>,
d124 3
a126 4
	    the <link
	      xlink:href="http://processorfinder.intel.com">Intel
	      Processor Spec Finder</link> for the definitive answer
	    about EM64T support in Intel processors.</para>
d151 1
a151 1
	  compatible</quote> machines.  Due to the wide range of
d158 1
a158 1
	point unit are supported.  All &intel; processors beginning
d228 5
a232 7
	at the <link
	  xlink:href="http://acpi.sourceforge.net/dsdt/index.php">DSDT</link>
	section of the <link
	  xlink:href="http://acpi.sourceforge.net/">ACPI4Linux</link>
	project Web site.  &os; can use these DSDTs to override the
	DSDT provided by the BIOS; see the &man.acpi.4; manual page
	for more information.</para>
d238 3
a240 4
      <para>Currently supported processors are the <link
	  xlink:href="http://people.freebsd.org/~marcel/refs/ia64/itanium/24532003.pdf">&itanium;</link>
	and the <link
	  xlink:href="http://people.freebsd.org/~marcel/refs/ia64/itanium2/25111003.pdf">&itanium; 2</link>.</para>
d263 1
a263 1
	exception is the VGA console.  The &os; support for VGA
d266 1
a266 1
	PC legacy support.  As such &man.syscons.4; cannot be enabled
d302 2
a303 2
      <para>All Apple PowerPC machines with built-in USB are
	supported, as well a limited selection of non-Apple machines,
d314 2
a315 2
	supported by &os; on the Fujitsu &sparc64; and Sun
	&ultrasparc; platforms.</para>
d325 2
a326 2
	&sun.blade; 100, &sun.blade; 150, &sun.ultra; 5 and
	&sun.ultra; 10) driver must use the serial console.</para>
d471 4
a474 5
	particular the fiber channel controllers in SBus-based systems
	are not supported.  However, it is possible to use these with
	a SCSI controller supported by the &man.esp.4; driver (Sun ESP
	SCSI, Sun FAS Fast-SCSI and Sun FAS366 Fast-Wide SCSI
	controllers).</para>
d486 3
a488 3
      <para>Starting with 7.2-RELEASE, &arch.sparc64; systems based on
	Sun &ultrasparc; III and beyond are also supported by &os;,
	which includes the following known working systems:</para>
d516 1
a516 2
	  <para>&sun.fire; V215 (support first appeared in 7.3-RELEASE
	    and 8.1-RELEASE)</para>
d524 1
a524 2
	  <para>&sun.fire; V245 (support first appeared in 7.3-RELEASE
	    and 8.1-RELEASE)</para>
d537 3
a539 4
	  <para>&sun.fire; V480 (501-6780 and 501-6790 centerplanes
	    only, for which support first appeared in 7.3-RELEASE and
	    8.1-RELEASE, other centerplanes might work beginning with
	    8.3-RELEASE and 9.0-RELEASE)</para>
d547 2
a548 3
	  <para>&sun.fire; V890 (support first appeared in 7.4-RELEASE
	    and 8.1-RELEASE, non-mixed &ultrasparc; IV/IV+
	    CPU-configurations only)</para>
d557 1
a557 1
	also believed to be supported by &os;:</para>
d565 2
a566 3
	  <para>&sun.fire; V490 (support first appeared in 7.4-RELEASE
	    and 8.1-RELEASE, non-mixed &ultrasparc; IV/IV+
	    CPU-configurations only)</para>
d570 3
a572 4
      <para>Starting with 7.4-RELEASE and 8.1-RELEASE, &arch.sparc64;
	systems based on Fujitsu &sparc64; V are also supported by
	&os;, which includes the following known working
	systems:</para>
d580 2
a581 2
      <para>The following Fujitsu &primepower; systems are not tested
	but also believed to be supported by &os;:</para>
a667 2
      &hwlist.aacraid;

d700 1
a700 1
	  controllers is supported.  EISA adapters are not
a711 2
      &hwlist.hptnr;

d730 1
a730 1
	  controllers is supported.  EISA adapters are not
d781 2
a782 2
	part of the <package>sysutils/cdrtools</package> port in the
	Ports Collection.</para>
a819 2
      &hwlist.alc;

a848 2
      &hwlist.cxgbe;

a1000 2
      &hwlist.ath.hal;

d1016 2
a1017 2
      <para>[&arch.i386;, &arch.amd64;] Marvell Libertas IEEE
	802.11b/g PCI network adapters (&man.malo.4; driver)</para>
d1138 2
a1139 2
	  <para>[&arch.amd64;, &arch.i386;] Avlab Technology, PCI IO
	    2S and PCI IO 4S</para>
d1143 1
a1143 2
	  <para>[&arch.amd64;, &arch.i386;] Comtrol RocketPort
	    550</para>
d1217 1
a1217 1
	    16C550/16C650/16C850</para>
d1300 1
a1300 1
	  configuration.</para>
d1449 1
a1449 2
	  USB Bluetooth adapters can be found in <link
	    linkend="bluetooth">Bluetooth</link> section.</para>
d1571 1
a1571 2
	  found at <uri
	    xlink:href="http://www.x.org/">http://www.x.org/</uri>.</para>
a1602 4
	  &hwlist.atp;
	</listitem>

	<listitem>
d1626 1
a1626 2
	  with <application>Xorg</application> can be found at <uri
	    xlink:href="http://www.x.org/">http://www.x.org/</uri>.</para>
d1659 2
a1660 3
	cards compatible with the HOT1 from <link
	  xlink:href="http://www.vcc.com/">Virtual Computers</link>
	(xrpu driver).</para>

CTMFN release/doc/en_US.ISO8859-1/readme/article.xml 1004 1004 644 b7d76b3c5a935f3b0f7932d3960484de f1840ea48701587c530ccad915ac4251 9840
d3 1
a3 1
  "../../../share/xml/freebsd50.dtd" [
d7 1
a7 1
<!--
d15 3
a17 4
<article xmlns="http://docbook.org/ns/docbook"
  xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
  <info>
    <title>&os; &release.current; README</title>
d21 1
a21 1
    <pubdate>$FreeBSD: stable/10/release/doc/en_US.ISO8859-1/readme/article.xml 270685 2014-08-26 23:58:54Z gjb $</pubdate>
d38 1
a38 3
      <year>2014</year>
      <holder role="mailto:doc@FreeBSD.org">The &os; Documentation
	Project</holder>
d49 7
a55 7
    <abstract>
      <para>This document gives a brief introduction to &os;
	&release.current;.  It includes some information on how to
	obtain &os;, a listing of various ways to contact the &os;
	Project, and pointers to some other sources of
	information.</para>
    </abstract>
d61 2
a62 3
    <para>This distribution is a &release.type; of &os;
      &release.current;, the latest point along the &release.branch;
      branch.</para>
d68 6
a73 6
	AMD64 and Intel EM64T based PC hardware (&arch.amd64;), Intel,
	AMD, Cyrix or NexGen <quote>x86</quote> based PC hardware
	(&arch.i386;), Intel Itanium Processor based computers
	(&arch.ia64;), NEC PC-9801/9821 series PCs and compatibles
	(&arch.pc98;), and &ultrasparc; machines (&arch.sparc64;).
	Versions for the &arm; (&arch.arm;), &mips; (&arch.mips;), and
d90 10
a99 10
	easy to obtain and install all your favorite traditional
	&unix; utilities for &os;.  Each <quote>port</quote> consists
	of a set of scripts to retrieve, configure, build, and install
	a piece of software, with a single command.  Over
	&os.numports; ports, from editors to programming languages to
	graphical applications, make &os; a powerful and comprehensive
	operating environment that extends far beyond what's provided
	by many commercial versions of &unix;.  Most ports are also
	available as pre-compiled <quote>packages</quote>, which can
	be quickly installed from the installation program.</para>
d105 40
a144 42
      <para releasetype="current">This &release.type; is aimed
	primarily at early adopters and various other users who want
	to get involved with the ongoing development of &os;.  While
	the &os; development team tries its best to ensure that each
	&release.type; works as advertised, &release.branch; is very
	much a work-in-progress.</para>

      <para releasetype="current">The basic requirements for using
	this &release.type; are technical proficiency with &os; and an
	understanding of the ongoing development process of &os;
	&release.branch; (as discussed on the &a.stable;).</para>

      <para releasetype="current">For those more interested in doing
	business with &os; than in experimenting with new &os;
	technology, formal releases (such as &release.prev.stable;)
	are frequently more appropriate.  Releases undergo a period of
	testing and quality assurance checking to ensure high
	reliability and dependability.</para>

      <para releasetype="snapshot">This &release.type; is aimed
	primarily at early adopters and various other users who want
	to get involved with the ongoing development of &os;.  While
	the &os; development team tries its best to ensure that each
	&release.type; works as advertised, &release.branch; is very
	much a work-in-progress.</para>

      <para releasetype="snapshot">The basic requirements for using
	this &release.type; are technical proficiency with &os; and an
	understanding of the ongoing development process of &os;
	&release.branch; (as discussed on the &a.stable;).</para>

      <para releasetype="snapshot">For those more interested in doing
	business with &os; than in experimenting with new &os;
	technology, formal releases (such as &release.prev.stable;)
	are frequently more appropriate.  Releases undergo a period of
	testing and quality assurance checking to ensure high
	reliability and dependability.</para>

      <para releasetype="release">This &release.type; of &os; is
	suitable for all users.  It has undergone a period of testing
	and quality assurance checking to ensure the highest
	reliability and dependability.</para>
d168 2
a169 3
	project are listed in the <link
	  xlink:href="&url.books.handbook;/mirrors.html"><quote>Obtaining
	    &os;</quote></link> appendix to the Handbook.</para>
d176 2
a177 3
	optional packages from <uri
	  xlink:href="ftp://ftp.FreeBSD.org/">ftp://ftp.FreeBSD.org/</uri>,
	which is the official &os; release site, or any of its
d189 2
a190 3
	information for mirror sites at the <link
	  xlink:href="&url.articles.hubs;/">Mirroring &os;</link>
	article.</para>
d210 1
a210 1
      <para>If tracking the &release.branch; development efforts, you
d215 5
a219 6
      <para>Being a largely-volunteer effort, the &os; Project is
	always happy to have extra hands willing to help&mdash;there
	are already far more desired enhancements than there is time
	to implement them.  To contact the developers on technical
	matters, or with offers of help, please send mail to the
	&a.hackers;.</para>
d228 7
a234 9
	wishing to do so.  Visit the <link
	  xlink:href="&url.base;/mailman/listinfo"> &os; Mailman Info
	  Page</link>.  This will give you more information on joining
	the various lists, accessing archives, etc.  There are
	a number of mailing lists targeted at special interest groups
	not mentioned here; more information can be obtained either
	from the Mailman pages or the <link
	  xlink:href="&url.base;/support.html#mailing-list">mailing
	  lists section</link> of the &os; Web site.</para>
d252 2
a253 2
	with Internet connectivity is to use the
	<application>Bugzilla</application> bug tracker.
d257 15
a271 13
	possible.  <link
	  xlink:href="https://bugs.FreeBSD.org/search/">A list of all
	  active PRs</link> is available on the &os; Web site; this
	list is useful to see what potential problems other users have
	encountered.</para>

      <para>Note that &man.send-pr.1; is deprecated.</para>

      <para>For more information, <link
	  xlink:href="&url.articles.problem-reports;/"><quote>Writing
	    &os; Problem Reports</quote></link>, available on the &os;
	Web site, has a number of helpful hints on writing and
	submitting effective problem reports.</para>
d290 2
a291 2
	may also include other formats such as Portable Document
	Format (<filename>.PDF</filename>).</para>
d293 33
a325 32
      <itemizedlist>
	<listitem>
	  <para><filename>README.TXT</filename>: This file, which
	    gives some general information about &os; as well as
	    some cursory notes about obtaining a
	    distribution.</para>
	</listitem>

	<listitem>
	  <para><filename>RELNOTES.TXT</filename>: The release
	    notes, showing what's new and different in &os;
	    &release.current; compared to the previous release (&os;
	    &release.prev;).</para>
	</listitem>

	<listitem>
	  <para><filename>HARDWARE.TXT</filename>: The hardware
	    compatibility list, showing devices with which &os; has
	    been tested and is known to work.</para>
	</listitem>

	<listitem>
	  <para><filename>ERRATA.TXT</filename>: Release errata.
	    Late-breaking, post-release information can be found in
	    this file, which is principally applicable to releases
	    (as opposed to snapshots).  It is important to consult
	    this file before installing a release of &os;, as it
	    contains the latest information on problems which have
	    been found and fixed since the release was
	    created.</para>
	</listitem>
      </itemizedlist>
d328 3
a330 4
	&arch.amd64;, &arch.i386;, &arch.ia64;, &arch.pc98;, and
	&arch.sparc64;), these documents are generally available via
	the Documentation menu during installation.  Once the system
	is installed, you can revisit this menu by re-running the
d342 2
a343 3
	  <uri
	    xlink:href="&url.base;/releases/">&url.base;/releases/</uri>
	  (as well as any sites which keep up-to-date mirrors of this
d351 6
a356 7
      <para>As with almost all &unix; like operating systems, &os;
	comes with a set of on-line manual pages, accessed through the
	&man.man.1; command or through the <link
	  xlink:href="http://www.FreeBSD.org/cgi/man.cgi">hypertext
	  manual pages gateway</link> on the &os; Web site.  In
	general, the manual pages provide information on the different
	commands and APIs available to the &os; user.</para>
d360 3
a362 3
	manual pages are &man.tuning.7; (a guide to performance
	tuning), &man.security.7; (an introduction to &os; security),
	and &man.style.9; (a style guide to kernel coding).</para>
d369 6
a374 8
	maintained by the &os; Project, are the &os; Handbook and &os;
	FAQ (Frequently Asked Questions document).  On-line versions
	of the <link
	  xlink:href="&url.books.handbook;/">Handbook</link> and <link
	  xlink:href="&url.books.faq;/">FAQ</link> are always
	available from the <link
	  xlink:href="&url.base;/docs.html">&os; Documentation
	  page</link> or its mirrors.  If you install the
d381 7
a387 7
	the &os; Project, cover more-specialized, &os;-related topics.
	This material spans a wide range of topics, from effective use
	of the mailing lists, to dual-booting &os; with other
	operating systems, to guidelines for new committers.  Like the
	Handbook and FAQ, these documents are available from the &os;
	Documentation Page or in the <filename>doc</filename>
	distribution set.</para>
d390 5
a394 6
	found in the <link
	  xlink:href="&url.books.handbook;/bibliography.html">bibliography</link>
	of the &os; Handbook.  Because of &os;'s strong &unix;
	heritage, many other articles and books written for &unix;
	systems are applicable as well, some of which are also listed
	in the bibliography.</para>
d403 4
a406 5
      countless hours to bring about this &release.type;.  For
      a complete list of &os; developers and contributors, please see
      <link
	xlink:href="&url.articles.contributors;/"><quote>Contributors
	  to &os;</quote></link> on the &os; Web site or any of its

CTMFN release/release.sh 1004 1004 755 5fff4da2652a5d2ec4b96fbdd557f172 174e27e137c9c58874ca03cdcbd25372 465
d36 1
a36 1
# $FreeBSD: stable/10/release/release.sh 270688 2014-08-27 00:50:51Z gjb $
a255 3
	REVISION=$(chroot ${CHROOTDIR} make -C /usr/src/release -V REVISION)
	BRANCH=$(chroot ${CHROOTDIR} make -C /usr/src/release -V BRANCH)
	UNAME_r=${REVISION}-${BRANCH}
d258 1
a258 2
		PBUILD_FLAGS="${PBUILD_FLAGS} UNAME_r=${UNAME_r}"
		PBUILD_FLAGS="${PBUILD_FLAGS} OSREL=${REVISION}"
d260 1
a260 2
			${PBUILD_FLAGS} OPTIONS_UNSET="FOP IGOR" \
			install clean distclean

CTMFN sys/amd64/include/vmm.h 1004 1004 644 885a76276391819ab96fa6d8b58e66da f2641c2130ce263ef0c6e61d41395c63 236
d26 1
a26 1
 * $FreeBSD: stable/10/sys/amd64/include/vmm.h 270696 2014-08-27 06:13:44Z grehan $
d590 1
a590 1
static __inline void
d596 1
a596 1
static __inline void
d602 1
a602 1
static __inline void
d608 1
a608 1
static __inline void

CTMFN sys/amd64/include/vmparam.h 1004 1004 644 35a4376ae04633b9f5a5d5760c25f860 a329dddc87cee3a6d4fc7bf89433a1bd 136
d41 1
a41 1
 * $FreeBSD: stable/10/sys/amd64/include/vmparam.h 270693 2014-08-27 01:34:33Z kib $
d90 1
a90 1
#define	VM_PHYSSEG_MAX		63

CTMFN sys/sys/exec.h 1004 1004 644 518d27d516610b6e38c72c5f31c7f50a 8660839f3e31ba9cd11fcb7ef51a4e36 844
d35 1
a35 1
 * $FreeBSD: stable/10/sys/sys/exec.h 270670 2014-08-26 19:58:48Z wblock $
d42 6
a47 11
 * Before ps_args existed, the following structure, found at the top of
 * the user stack of each user process, was used by ps(1) to locate
 * environment and argv strings.  Normally ps_argvstr points to the
 * argv vector, and ps_nargvstr is the same as the program's argc. The
 * fields ps_envstr and ps_nenvstr are the equivalent for the environment.
 *
 * Programs should now use setproctitle(3) to change ps output.
 * setproctitle() always informs the kernel with sysctl and sets the
 * pointers in ps_strings.  The kern.proc.args sysctl first tries p_args.
 * If p_args is NULL, it then falls back to reading ps_strings and following
 * the pointers.
a57 1
 * Prefer the kern.ps_strings or kern.proc.ps_strings sysctls to this constant.

CTMFN sys/ufs/ffs/ffs_vfsops.c 1004 1004 644 add8c28fd7847d7259953cbc6a65e039 c2f4e1406ba8e18f53fa944bf3cd8534 148
d33 1
a33 1
__FBSDID("$FreeBSD: stable/10/sys/ufs/ffs/ffs_vfsops.c 270694 2014-08-27 01:37:22Z kib $");
d1216 1
a1216 1
		susp = fs->fs_ronly == 0;

CTMFN sys/ufs/ufs/ufs_vnops.c 1004 1004 644 d31e5db3cb93e975b9387f951f0de13d f7f8dd74130b8cfda11021fe2c771e55 127
d38 1
a38 1
__FBSDID("$FreeBSD: stable/10/sys/ufs/ufs/ufs_vnops.c 270695 2014-08-27 01:38:26Z kib $");
d1145 5
d1549 2
d1568 2

CTM_END 57dd7f4d573502f076a8c6a7a7239973