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

Consistently use the command tag instead of the quote tag:

Browse source 
s/<quote>make buildworld</quote>/<command>make buildworld</command>/
and
s/<quote>make installworld</quote>/<command>make installworld</command>/

Discussed with:		blackend
Approved by:		simon (mentor)
This commit is contained in:
Remko Lodder 2004-12-12 17:52:47 +00:00
parent 9681b56a3b
commit fa6dfdba31
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=23189
1 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -690,10 +690,10 @@
<filename>/etc/group</filename>.</para>
<para>There have been occasions when the installation part of
<quote>make installworld</quote> has expected certain usernames or groups
<command>make installworld</command> has expected certain usernames or groups
to exist. When performing an upgrade it is likely that these
users or groups did not exist. This caused problems when upgrading.
In some cases <quote>make buildworld</quote> will check to see if
In some cases <command>make buildworld</command> will check to see if
these users or groups exist.</para>
<para>A recent example of this is when the
@ -799,7 +799,7 @@
<filename>/usr/obj</filename>. The directories shadow those under
<filename>/usr/src</filename>.</para>
<para>You can speed up the <quote>make buildworld</quote> process, and
<para>You can speed up the <command>make buildworld</command> process, and
possibly save yourself some dependency headaches by removing this
directory as well.</para>
@ -1528,14 +1528,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 buildworld</quote> process is to
of the first steps in the <command>make buildworld</command> 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 340&nbsp;MB).</para>
<para>However, if you know what you are doing you can have
<quote>make buildworld</quote> skip this step. This will make subsequent
<command>make buildworld</command> 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.
@ -1556,7 +1556,7 @@ Script done, &hellip;</screen>
you found a problem.</para>
<para><emphasis>In general</emphasis> (and this is not a hard and
fast rule) the <quote>make buildworld</quote> process builds new
fast rule) the <command>make buildworld</command> process builds new
copies of essential tools (such as &man.gcc.1;, and
&man.make.1;) and the system libraries. These tools and
libraries are then installed. The new tools and libraries are
@ -1574,7 +1574,7 @@ Script done, &hellip;</screen>
&prompt.root; <userinput>make -DNOCLEAN all</userinput></screen>
<para>This will not undo the work of the previous
<quote>make buildworld</quote>.</para>
<command>make buildworld</command>.</para>
<para>If you see the message:</para>
@ -1582,7 +1582,7 @@ Script done, &hellip;</screen>
Building everything..
--------------------------------------------------------------</screen>
<para>in the <quote>make buildworld</quote> output then it is
<para>in the <command>make buildworld</command> output then it is
probably fairly safe to do so.</para>
<para>If you do not see that message, or you are not sure, then it