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

Various fixes:

Browse source 
. Fix title of a section.
. Fix grammar in a few places.
. Always use <quote>...</quote> instead of <quote/.../ for quoting.
. Use an entity when referring to make(1) as a command.
. Remove the 'living dangerously' part until I find better words to
  describe it, or someone comes up with a better way to describe all
  the possible variables one can use while building world.

PR:		docs/38880
Submitted by:	Chris Pepper <pepper@reppep.com>
This commit is contained in:
Giorgos Keramidas 2002-06-23 21:13:50 +00:00
parent ce67c66952
commit c47877c801
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=13465
1 changed files with 6 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -683,7 +683,7 @@ subscribe cvs-all</programlisting>
</sect2>
<sect2>
<title>Update the files of <filename>/etc</filename></title>
<title>Update the files in <filename>/etc</filename></title>
<para>The <filename>/etc</filename> directory contains a large part
of your system's configuration information, as well as scripts
@ -1205,7 +1205,7 @@ Script done, &hellip;</screen>
files, determining how they differ with your existing files.</para>
<para>Note that some of the files that will have been installed in
<filename>/var/tmp/root</filename> have a leading <quote/./. At the
<filename>/var/tmp/root</filename> have a leading <quote>.</quote>. At the
time of writing the only files like this are shell startup files in
<filename>/var/tmp/root/</filename> and
<filename>/var/tmp/root/root/</filename>, although there may be others
@ -1451,7 +1451,7 @@ Script done, &hellip;</screen>
<para>At the end of the day, it is your call. You might be happy
re-making the world every fortnight say, and let changes
accumulate over that fortnight. Or you might want to re-make
just those things that have changed, and are confident you can
just those things that have changed, and be confident you can
spot all the dependencies.</para>
<para>And, of course, this all depends on how often you want to
@ -1495,14 +1495,14 @@ Script done, &hellip;</screen>
<para><filename>/usr/obj</filename> contains all the object files
that were produced during the compilation phase. Normally, one
of the first steps in the <quote/make world/ process is to
of the first steps in the <quote>make world</quote> process is to
remove this directory and start afresh. In this case, keeping
<filename>/usr/obj</filename> around after you have finished
makes little sense, and will free up a large chunk of disk space
(currently about 340MB).</para>
<para>However, if you know what you are doing you can have
<quote/make world/ skip this step. This will make subsequent
<quote>make world</quote> skip this step. This will make subsequent
builds run much faster, since most of sources will not need to
be recompiled. The flip side of this is that subtle dependency
problems can creep in, causing your build to fail in odd ways.
@ -1510,12 +1510,6 @@ Script done, &hellip;</screen>
when one person complains that their build has failed, not
realising that it is because they have tried to cut
corners.</para>
<para>If you want to live dangerously then make the world, passing
the <makevar>NOCLEAN</makevar> definition to <command>make</command>, like
this:</para>
<screen>&prompt.root; <userinput>make -DNOCLEAN world</userinput></screen>
</answer>
</qandaentry>
@ -1606,7 +1600,7 @@ Building everything..
</listitem>
<listitem>
<para>Pass the <option>-j&lt;n&gt;</option> option to make to
<para>Pass the <option>-j&lt;n&gt;</option> option to &man.make.1; to
run multiple processes in parallel. This usually helps
regardless of whether you have a single or a multi processor
machine.</para>