os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Clean up previous changes, and remove the last references to

Browse source 
releases that are years old. Note that the cvs log for revision 1.66
should have said moving away from this old information, not to it.

Approved by:	murray
This commit is contained in:
Eric Melville 2001-05-12 03:20:47 +00:00
parent a0dc93d3a5
commit 782bd4543d
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9416
2 changed files with 34 additions and 48 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

41
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.66 2001/05/01 08:04:52 eric Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.67 2001/05/01 10:40:37 kuriyama Exp $
-->
<chapter id="cutting-edge">
@ -606,7 +606,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
trouble.</para>
<para>Another method is to compile the system in multi-user mode, and
then drop into single user mode for the installation. If you would
then drop into single user mode for the installation. If you would
like to do it this way, simply hold off on the following steps until
the build has completed.</para>
@ -660,7 +660,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<para>It is a good idea to save the output you get from running
&man.make.1; to another file. If something goes wrong you will
have a copy of the error message. While this might not help you
have a copy of the error message. While this might not help you
in diagnosing what has gone wrong, it can help others if you post
your problem to one of the FreeBSD mailing lists.</para>
@ -784,7 +784,7 @@ Script done, &hellip;</screen>
<para>It is now possible to specify a -j option to
<command>make</command> which will cause it to spawn several
simultaneous processes. This is most useful on multi-CPU machines.
simultaneous processes. This is most useful on multi-CPU machines.
However, since much of the compiling process is IO bound rather
than CPU bound it is also useful on single CPU machines.</para>
@ -812,7 +812,7 @@ Script done, &hellip;</screen>
<para>Many factors influence the build time, but currently a 500mhz
Pentium 3 with 128MB of RAM takes about 3 and a half hours to build
the -CURRENT tree, with no tricks or shortcuts used during the
process. A -STABLE tree will build somewhat faster.</para>
process. A -STABLE tree will build somewhat faster.</para>
</sect3>
</sect2>
@ -1073,7 +1073,7 @@ Script done, &hellip;</screen>
<para>In most cases, the &man.mergemaster.8 tool will realize when
it is necessary to update the devices, and offer to complete it
automatically. These instructions tell how to update the devices
automatically. These instructions tell how to update the devices
manually.</para>
<para>For safety's sake, this is a multi-step process.</para>
@ -1325,10 +1325,10 @@ Building everything..
<answer>
<para>This is a fairly easy task, and can save hours of compile
time for many machines. Simply run the buildworld on a central
time for many machines. Simply run the buildworld on a central
machine, and then NFS mount <filename>/usr/src</filename> and
<filename>/usr/obj</filename> on the remote machine and install
it there.</para>
<filename>/usr/obj</filename> on the remote machine and
installworld there.</para>
</answer>
</qandaentry>
@ -1349,7 +1349,7 @@ Building everything..
</listitem>
<listitem>
<para>Better still, put these filesystems across separate
<para>Better still, put these filesystems across multiple
disks using the <quote>ccd</quote> (concatenated disk
driver) device.</para>
</listitem>
@ -1363,7 +1363,7 @@ Building everything..
<listitem>
<para>Also in <filename>/etc/make.conf</filename>, set
<quote>CFLAGS</quote> to something like <quote>-O
-pipe</quote>. The optimization <quote>-O2</quote> is much
-pipe</quote>. The optimization <quote>-O2</quote> is much
slower, and the optimization difference between
<quote>-O</quote> and <quote>-O2</quote> is normally
negligible. <quote>-pipe</quote> lets the compiler use
@ -1372,24 +1372,17 @@ Building everything..
</listitem>
<listitem>
<para>Pass the <option>-j&lt;n&gt;</option> option to make (if
you are running a sufficiently recent version of FreeBSD) to
run multiple processes in parallel. This helps regardless
of whether you have a single or a multi processor
<para>Pass the <option>-j&lt;n&gt;</option> option to make to
run multiple processes in parallel. This usually helps
regardless of whether you have a single or a multi processor
machine.</para>
</listitem>
<listitem><para>The filesystem holding
<filename>/usr/src</filename> can be mounted (or remounted)
with the <quote>noatime</quote> option. This stops the time
files in the filesystem were last accessed from being
written to the disk. You probably do not need this
information anyway.
<note>
<para><quote>noatime</quote> is in version 2.2.0 and
above.</para>
</note>
with the <quote>noatime</quote> option. This prevents the
filesystem from recording the file access time. You probably
do not need this information anyway.
<screen>&prompt.root; <userinput>mount -u -o noatime /usr/src</userinput></screen>

41
en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.66 2001/05/01 08:04:52 eric Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.67 2001/05/01 10:40:37 kuriyama Exp $
-->
<chapter id="cutting-edge">
@ -606,7 +606,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
trouble.</para>
<para>Another method is to compile the system in multi-user mode, and
then drop into single user mode for the installation. If you would
then drop into single user mode for the installation. If you would
like to do it this way, simply hold off on the following steps until
the build has completed.</para>
@ -660,7 +660,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<para>It is a good idea to save the output you get from running
&man.make.1; to another file. If something goes wrong you will
have a copy of the error message. While this might not help you
have a copy of the error message. While this might not help you
in diagnosing what has gone wrong, it can help others if you post
your problem to one of the FreeBSD mailing lists.</para>
@ -784,7 +784,7 @@ Script done, &hellip;</screen>
<para>It is now possible to specify a -j option to
<command>make</command> which will cause it to spawn several
simultaneous processes. This is most useful on multi-CPU machines.
simultaneous processes. This is most useful on multi-CPU machines.
However, since much of the compiling process is IO bound rather
than CPU bound it is also useful on single CPU machines.</para>
@ -812,7 +812,7 @@ Script done, &hellip;</screen>
<para>Many factors influence the build time, but currently a 500mhz
Pentium 3 with 128MB of RAM takes about 3 and a half hours to build
the -CURRENT tree, with no tricks or shortcuts used during the
process. A -STABLE tree will build somewhat faster.</para>
process. A -STABLE tree will build somewhat faster.</para>
</sect3>
</sect2>
@ -1073,7 +1073,7 @@ Script done, &hellip;</screen>
<para>In most cases, the &man.mergemaster.8 tool will realize when
it is necessary to update the devices, and offer to complete it
automatically. These instructions tell how to update the devices
automatically. These instructions tell how to update the devices
manually.</para>
<para>For safety's sake, this is a multi-step process.</para>
@ -1325,10 +1325,10 @@ Building everything..
<answer>
<para>This is a fairly easy task, and can save hours of compile
time for many machines. Simply run the buildworld on a central
time for many machines. Simply run the buildworld on a central
machine, and then NFS mount <filename>/usr/src</filename> and
<filename>/usr/obj</filename> on the remote machine and install
it there.</para>
<filename>/usr/obj</filename> on the remote machine and
installworld there.</para>
</answer>
</qandaentry>
@ -1349,7 +1349,7 @@ Building everything..
</listitem>
<listitem>
<para>Better still, put these filesystems across separate
<para>Better still, put these filesystems across multiple
disks using the <quote>ccd</quote> (concatenated disk
driver) device.</para>
</listitem>
@ -1363,7 +1363,7 @@ Building everything..
<listitem>
<para>Also in <filename>/etc/make.conf</filename>, set
<quote>CFLAGS</quote> to something like <quote>-O
-pipe</quote>. The optimization <quote>-O2</quote> is much
-pipe</quote>. The optimization <quote>-O2</quote> is much
slower, and the optimization difference between
<quote>-O</quote> and <quote>-O2</quote> is normally
negligible. <quote>-pipe</quote> lets the compiler use
@ -1372,24 +1372,17 @@ Building everything..
</listitem>
<listitem>
<para>Pass the <option>-j&lt;n&gt;</option> option to make (if
you are running a sufficiently recent version of FreeBSD) to
run multiple processes in parallel. This helps regardless
of whether you have a single or a multi processor
<para>Pass the <option>-j&lt;n&gt;</option> option to make to
run multiple processes in parallel. This usually helps
regardless of whether you have a single or a multi processor
machine.</para>
</listitem>
<listitem><para>The filesystem holding
<filename>/usr/src</filename> can be mounted (or remounted)
with the <quote>noatime</quote> option. This stops the time
files in the filesystem were last accessed from being
written to the disk. You probably do not need this
information anyway.
<note>
<para><quote>noatime</quote> is in version 2.2.0 and
above.</para>
</note>
with the <quote>noatime</quote> option. This prevents the
filesystem from recording the file access time. You probably
do not need this information anyway.
<screen>&prompt.root; <userinput>mount -u -o noatime /usr/src</userinput></screen>