Whitespace-only change:
remove multiple spaces that are `inside' sentences. Partially from: docs/39858
This commit is contained in:
parent
48e11e821c
commit
e3ae5c7490
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=13623
1 changed files with 14 additions and 14 deletions
|
@ -238,7 +238,7 @@ subscribe cvs-all</programlisting>
|
|||
with <ulink
|
||||
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/standard-supfile">this
|
||||
supfile</ulink>. This is the most recommended
|
||||
method, since it allows you to grab the entire
|
||||
method, since it allows you to grab the entire
|
||||
collection once and then only what has changed from then
|
||||
on. Many people run <command>cvsup</command> from
|
||||
<command>cron</command> and keep their
|
||||
|
@ -441,7 +441,7 @@ subscribe cvs-all</programlisting>
|
|||
with <ulink
|
||||
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/stable-supfile">this
|
||||
supfile</ulink>. This is the most recommended
|
||||
method, since it allows you to grab the entire
|
||||
method, since it allows you to grab the entire
|
||||
collection once and then only what has changed from then
|
||||
on. Many people run <command>cvsup</command> from
|
||||
<command>cron</command> to keep their
|
||||
|
@ -615,7 +615,7 @@ subscribe cvs-all</programlisting>
|
|||
|
||||
<indexterm><primary>mailing list</primary></indexterm>
|
||||
<para>The &os.stable; and &os.current; branches are, by their
|
||||
nature, <emphasis>in development</emphasis>. People that
|
||||
nature, <emphasis>in development</emphasis>. People that
|
||||
contribute to &os; are human, and mistakes occasionally
|
||||
happen.</para>
|
||||
|
||||
|
@ -625,7 +625,7 @@ subscribe cvs-all</programlisting>
|
|||
filesystems (or worse).</para>
|
||||
|
||||
<para>If problems like these occur, a <quote>heads up</quote> is
|
||||
posted to the appropriate mailing list, explaining the nature of
|
||||
posted to the appropriate mailing list, explaining the nature of
|
||||
the problem and which systems it affects. And an <quote>all
|
||||
clear</quote> announcement is posted when the problem has been
|
||||
solved.</para>
|
||||
|
@ -746,7 +746,7 @@ subscribe cvs-all</programlisting>
|
|||
from the obvious benefit of making things go slightly faster,
|
||||
reinstalling the system will touch a lot of important system
|
||||
files, all the standard system binaries, libraries, include files
|
||||
and so on. Changing these on a running system (particularly if
|
||||
and so on. Changing these on a running system (particularly if
|
||||
you have active users on the system at the time) is asking for
|
||||
trouble.</para>
|
||||
|
||||
|
@ -799,7 +799,7 @@ subscribe cvs-all</programlisting>
|
|||
<filename>/usr/src</filename>.</para>
|
||||
|
||||
<para>You can speed up the <quote>make world</quote> process, and
|
||||
possibly save yourself some dependency headaches by removing this
|
||||
possibly save yourself some dependency headaches by removing this
|
||||
directory as well.</para>
|
||||
|
||||
<para>Some files below <filename>/usr/obj</filename> may have the
|
||||
|
@ -1045,7 +1045,7 @@ Script done, …</screen>
|
|||
&prompt.root; <userinput>make installworld</userinput></screen>
|
||||
|
||||
<note>
|
||||
<para>If you specified variables on the <command>make
|
||||
<para>If you specified variables on the <command>make
|
||||
buildworld</command> command line, you must specify the same
|
||||
variables in the <command>make installworld</command> command
|
||||
line. This does not necessarily hold true for other options;
|
||||
|
@ -1152,7 +1152,7 @@ Script done, …</screen>
|
|||
first. This is because the <filename>/usr/src/etc</filename>
|
||||
directory <emphasis>is not</emphasis> a copy of what your
|
||||
<filename>/etc</filename> directory should look like. In addition,
|
||||
there are files that should be in <filename>/etc</filename> that are
|
||||
there are files that should be in <filename>/etc</filename> that are
|
||||
not in <filename>/usr/src/etc</filename>.</para>
|
||||
|
||||
<para>If you are using &man.mergemaster.8; (as recommended),
|
||||
|
@ -1234,7 +1234,7 @@ Script done, …</screen>
|
|||
|
||||
<para>You can speed this process up by keeping a copy of the last set
|
||||
of changed files that you merged into <filename>/etc</filename>.
|
||||
The following procedure gives one idea of how to do this.</para>
|
||||
The following procedure gives one idea of how to do this.</para>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
|
@ -1292,7 +1292,7 @@ Script done, …</screen>
|
|||
|
||||
<step>
|
||||
<para>Repeat this process every time you need to merge in changes
|
||||
to <filename>/etc</filename>.</para>
|
||||
to <filename>/etc</filename>.</para>
|
||||
</step>
|
||||
</procedure>
|
||||
|
||||
|
@ -1339,7 +1339,7 @@ Script done, …</screen>
|
|||
|
||||
<step>
|
||||
<para>Now, take a snapshot of your current
|
||||
<filename>/dev</filename>. This snapshot needs to contain the
|
||||
<filename>/dev</filename>. This snapshot needs to contain the
|
||||
permissions, ownerships, major and minor numbers of each filename,
|
||||
but it should not contain the time stamps. The easiest way to do
|
||||
this is to use &man.awk.1; to strip out some of the
|
||||
|
@ -1385,8 +1385,8 @@ Script done, …</screen>
|
|||
<para>For the sake of completeness, you may want to update the files in
|
||||
<filename>/stand</filename> as well. These files consist of hard
|
||||
links to the <filename>/stand/sysinstall</filename> binary. This
|
||||
binary should be statically linked, so that it can work when no other
|
||||
filesystems (and in particular <filename>/usr</filename>) have been
|
||||
binary should be statically linked, so that it can work when no other
|
||||
filesystems (and in particular <filename>/usr</filename>) have been
|
||||
mounted.</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/src/release/sysinstall</userinput>
|
||||
|
@ -1618,7 +1618,7 @@ Building everything..
|
|||
<para>The example assumes <filename>/usr/src</filename> is
|
||||
on its own filesystem. If it is not (if it is a part of
|
||||
<filename>/usr</filename> for example) then you will
|
||||
need to use that filesystem mount point, and not
|
||||
need to use that filesystem mount point, and not
|
||||
<filename>/usr/src</filename>.</para>
|
||||
</warning>
|
||||
</para>
|
||||
|
|
Loading…
Reference in a new issue