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

Remove references to the pronoun "I". Other than being informal, all

Browse source 
it does is make someone wonder who this "I" is.
This commit is contained in:
Dima Dorfman 2001-04-16 20:47:01 +00:00
parent eac4f5a1de
commit cc7a5aca98
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9207
2 changed files with 80 additions and 74 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -1,7 +1,7 @@
<!-- <!--
The FreeBSD Documentation Project The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.61 2001/04/09 00:33:49 dd Exp $ $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.62 2001/04/12 07:34:04 nik Exp $
--> -->
<chapter id="cutting-edge"> <chapter id="cutting-edge">
@ -109,10 +109,10 @@
nasty people who do not like helping people out (we would nasty people who do not like helping people out (we would
not even be doing FreeBSD if we were), it is literally not even be doing FreeBSD if we were), it is literally
because we cannot answer 400 messages a day because we cannot answer 400 messages a day
<emphasis>and</emphasis> actually work on FreeBSD! I am <emphasis>and</emphasis> actually work on FreeBSD! Given the
sure that, if given the choice between having us answer lots choice between improving FreeBSD and answering lots of
of questions or continuing to improve FreeBSD, most of you questions, most developers, and users, would probably opt for
would vote for us improving it.</para> the former.</para>
</listitem> </listitem>
</orderedlist> </orderedlist>
</sect3> </sect3>
@ -471,7 +471,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<warning> <warning>
<title>Take a backup</title> <title>Take a backup</title>
<para>I cannot stress highly enough how important it is to take a <para>It cannot be stressed enough how important it is to take a
backup of your system <emphasis>before</emphasis> you do this. backup of your system <emphasis>before</emphasis> you do this.
While remaking the world is (as long as you follow these While remaking the world is (as long as you follow these
instructions) an easy task to do, there will inevitably be times instructions) an easy task to do, there will inevitably be times
@ -479,8 +479,8 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
source tree render your system unbootable.</para> source tree render your system unbootable.</para>
<para>Make sure you have taken a backup. And have a fix-it floppy to <para>Make sure you have taken a backup. And have a fix-it floppy to
hand. I have never needed to use them, and, touch wood, I never hand. You will probably never have to use it, but it is better to be
will, but it is always better to be safe than sorry.</para> safe than sorry!</para>
</warning> </warning>
<warning> <warning>
@ -795,14 +795,15 @@ Script done, &hellip;</screen>
and <maketarget>installworld</maketarget> installs this tree on and <maketarget>installworld</maketarget> installs this tree on
the current machine.</para> the current machine.</para>
<para>This is very useful for 2 reasons. First, it allows you to do <para>This is very useful for 2 reasons. First, it allows you
the build safe in the knowledge that no components of your running to do the build safe in the knowledge that no components of
system will be affected. The build is <quote>self hosted</quote>. your running system will be affected. The build is
Because of this, you can safely run <quote>self hosted</quote>. Because of this, you can safely
<maketarget>buildworld</maketarget> on a machine running in run <maketarget>buildworld</maketarget> on a machine running
multi-user mode with no fear of ill-effects. I still recommend you in multi-user mode with no fear of ill-effects. It is still
run the <maketarget>installworld</maketarget> part in single user recommended that you run the
mode though.</para> <maketarget>installworld</maketarget> part in single user
mode, though.</para>
<para>Secondly, it allows you to use NFS mounts to upgrade <para>Secondly, it allows you to use NFS mounts to upgrade
multiple machines on your network. If you have three machines, multiple machines on your network. If you have three machines,
@ -980,8 +981,8 @@ Script done, &hellip;</screen>
</warning> </warning>
<para>You need to build a dummy set of directories to install the new <para>You need to build a dummy set of directories to install the new
<filename>/etc</filename> and other files into. I generally choose to <filename>/etc</filename> and other files into.
put this dummy directory in <filename>/var/tmp/root</filename>, and <filename>/var/tmp/root</filename> is a reasonable choice, and
there are a number of subdirectories required under this as there are a number of subdirectories required under this as
well.</para> well.</para>
@ -1214,16 +1215,14 @@ Script done, &hellip;</screen>
<para>You should now have successfully upgraded your FreeBSD system. <para>You should now have successfully upgraded your FreeBSD system.
Congratulations.</para> Congratulations.</para>
<para>You may notice small problems due to things that you have missed. <para>You may notice small problems due to things that you have
For example, I once deleted <filename>/etc/magic</filename> as part of missed. For example, if you accidently deleted
the upgrade and merge to <filename>/etc</filename>, and the <filename>/etc/magic</filename> as part of the upgrade or merge of
<command>file</command> command stopped working. A moment's thought <filename>/etc</filename>, the &man.file.1; command will stop
meant that working. In this case, the fix would be to run:</para>
<screen>&prompt.root; <userinput>cd /usr/src/usr.bin/file</userinput> <screen>&prompt.root; <userinput>cd /usr/src/usr.bin/file</userinput>
&prompt.root; <userinput/make all install/</screen> &prompt.root; <userinput/make all install/</screen>
was sufficient to fix that one.</para>
</sect2> </sect2>
<sect2> <sect2>
@ -1237,9 +1236,8 @@ Script done, &hellip;</screen>
<answer> <answer>
<para>There is no easy answer to this one, as it depends on the <para>There is no easy answer to this one, as it depends on the
nature of the change. For example, I have just run CVSup, and nature of the change. For example, if you just ran CVSup, and
it has shown the following files as being updated since I last it has shown the following files as being updated,</para>
ran it;</para>
<screen><filename>src/games/cribbage/instr.c</filename> <screen><filename>src/games/cribbage/instr.c</filename>
<filename>src/games/sail/pl_main.c</filename> <filename>src/games/sail/pl_main.c</filename>
@ -1247,13 +1245,13 @@ Script done, &hellip;</screen>
<filename>src/release/sysinstall/media.c</filename> <filename>src/release/sysinstall/media.c</filename>
<filename>src/share/mk/bsd.port.mk</filename></screen> <filename>src/share/mk/bsd.port.mk</filename></screen>
<para>There is nothing in there that I would re-make the world <para>it probably is not worth rebuilding the entire world.
for. I would go to the appropriate sub-directories and You could just go to the appropriate sub-directories and
<command>make all install</command>, and that's about it. But <command>make all install</command>, and that's about it. But
if something major changed, for example if something major changed, for example
<filename>src/lib/libc/stdlib</filename> then I would either <filename>src/lib/libc/stdlib</filename> then you should either
re-make the world, or at least those parts of it that are re-make the world, or at least those parts of it that are
statically linked (as well as anything else I might have added statically linked (as well as anything else you might have added
that is statically linked).</para> that is statically linked).</para>
<para>At the end of the day, it is your call. You might be happy <para>At the end of the day, it is your call. You might be happy
@ -1383,12 +1381,17 @@ Building everything..
results of that compile to <command>make install</command> on to results of that compile to <command>make install</command> on to
other machines around the network.</para> other machines around the network.</para>
<para>This is not something I have done, so the suggestions below <para>
are either from other people, or deduced from the <warning>
Makefiles.</para> <para>The following suggestions are not well tested or
officially supported; they were derived either from
posts on a mailing list or from the Makefiles. Use
them at your own risk.</para>
</warning>
</para>
<para>The precise approach to take depends on your version of <para>The precise approach to take depends on your version of
FreeBSD</para> FreeBSD.</para>
<para>You must still upgrade <filename>/etc</filename> and <para>You must still upgrade <filename>/etc</filename> and
<filename>/dev</filename> on the target machines after doing <filename>/dev</filename> on the target machines after doing

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

@ -1,7 +1,7 @@
<!-- <!--
The FreeBSD Documentation Project The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.61 2001/04/09 00:33:49 dd Exp $ $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.62 2001/04/12 07:34:04 nik Exp $
--> -->
<chapter id="cutting-edge"> <chapter id="cutting-edge">
@ -109,10 +109,10 @@
nasty people who do not like helping people out (we would nasty people who do not like helping people out (we would
not even be doing FreeBSD if we were), it is literally not even be doing FreeBSD if we were), it is literally
because we cannot answer 400 messages a day because we cannot answer 400 messages a day
<emphasis>and</emphasis> actually work on FreeBSD! I am <emphasis>and</emphasis> actually work on FreeBSD! Given the
sure that, if given the choice between having us answer lots choice between improving FreeBSD and answering lots of
of questions or continuing to improve FreeBSD, most of you questions, most developers, and users, would probably opt for
would vote for us improving it.</para> the former.</para>
</listitem> </listitem>
</orderedlist> </orderedlist>
</sect3> </sect3>
@ -471,7 +471,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<warning> <warning>
<title>Take a backup</title> <title>Take a backup</title>
<para>I cannot stress highly enough how important it is to take a <para>It cannot be stressed enough how important it is to take a
backup of your system <emphasis>before</emphasis> you do this. backup of your system <emphasis>before</emphasis> you do this.
While remaking the world is (as long as you follow these While remaking the world is (as long as you follow these
instructions) an easy task to do, there will inevitably be times instructions) an easy task to do, there will inevitably be times
@ -479,8 +479,8 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
source tree render your system unbootable.</para> source tree render your system unbootable.</para>
<para>Make sure you have taken a backup. And have a fix-it floppy to <para>Make sure you have taken a backup. And have a fix-it floppy to
hand. I have never needed to use them, and, touch wood, I never hand. You will probably never have to use it, but it is better to be
will, but it is always better to be safe than sorry.</para> safe than sorry!</para>
</warning> </warning>
<warning> <warning>
@ -795,14 +795,15 @@ Script done, &hellip;</screen>
and <maketarget>installworld</maketarget> installs this tree on and <maketarget>installworld</maketarget> installs this tree on
the current machine.</para> the current machine.</para>
<para>This is very useful for 2 reasons. First, it allows you to do <para>This is very useful for 2 reasons. First, it allows you
the build safe in the knowledge that no components of your running to do the build safe in the knowledge that no components of
system will be affected. The build is <quote>self hosted</quote>. your running system will be affected. The build is
Because of this, you can safely run <quote>self hosted</quote>. Because of this, you can safely
<maketarget>buildworld</maketarget> on a machine running in run <maketarget>buildworld</maketarget> on a machine running
multi-user mode with no fear of ill-effects. I still recommend you in multi-user mode with no fear of ill-effects. It is still
run the <maketarget>installworld</maketarget> part in single user recommended that you run the
mode though.</para> <maketarget>installworld</maketarget> part in single user
mode, though.</para>
<para>Secondly, it allows you to use NFS mounts to upgrade <para>Secondly, it allows you to use NFS mounts to upgrade
multiple machines on your network. If you have three machines, multiple machines on your network. If you have three machines,
@ -980,8 +981,8 @@ Script done, &hellip;</screen>
</warning> </warning>
<para>You need to build a dummy set of directories to install the new <para>You need to build a dummy set of directories to install the new
<filename>/etc</filename> and other files into. I generally choose to <filename>/etc</filename> and other files into.
put this dummy directory in <filename>/var/tmp/root</filename>, and <filename>/var/tmp/root</filename> is a reasonable choice, and
there are a number of subdirectories required under this as there are a number of subdirectories required under this as
well.</para> well.</para>
@ -1214,16 +1215,14 @@ Script done, &hellip;</screen>
<para>You should now have successfully upgraded your FreeBSD system. <para>You should now have successfully upgraded your FreeBSD system.
Congratulations.</para> Congratulations.</para>
<para>You may notice small problems due to things that you have missed. <para>You may notice small problems due to things that you have
For example, I once deleted <filename>/etc/magic</filename> as part of missed. For example, if you accidently deleted
the upgrade and merge to <filename>/etc</filename>, and the <filename>/etc/magic</filename> as part of the upgrade or merge of
<command>file</command> command stopped working. A moment's thought <filename>/etc</filename>, the &man.file.1; command will stop
meant that working. In this case, the fix would be to run:</para>
<screen>&prompt.root; <userinput>cd /usr/src/usr.bin/file</userinput> <screen>&prompt.root; <userinput>cd /usr/src/usr.bin/file</userinput>
&prompt.root; <userinput/make all install/</screen> &prompt.root; <userinput/make all install/</screen>
was sufficient to fix that one.</para>
</sect2> </sect2>
<sect2> <sect2>
@ -1237,9 +1236,8 @@ Script done, &hellip;</screen>
<answer> <answer>
<para>There is no easy answer to this one, as it depends on the <para>There is no easy answer to this one, as it depends on the
nature of the change. For example, I have just run CVSup, and nature of the change. For example, if you just ran CVSup, and
it has shown the following files as being updated since I last it has shown the following files as being updated,</para>
ran it;</para>
<screen><filename>src/games/cribbage/instr.c</filename> <screen><filename>src/games/cribbage/instr.c</filename>
<filename>src/games/sail/pl_main.c</filename> <filename>src/games/sail/pl_main.c</filename>
@ -1247,13 +1245,13 @@ Script done, &hellip;</screen>
<filename>src/release/sysinstall/media.c</filename> <filename>src/release/sysinstall/media.c</filename>
<filename>src/share/mk/bsd.port.mk</filename></screen> <filename>src/share/mk/bsd.port.mk</filename></screen>
<para>There is nothing in there that I would re-make the world <para>it probably is not worth rebuilding the entire world.
for. I would go to the appropriate sub-directories and You could just go to the appropriate sub-directories and
<command>make all install</command>, and that's about it. But <command>make all install</command>, and that's about it. But
if something major changed, for example if something major changed, for example
<filename>src/lib/libc/stdlib</filename> then I would either <filename>src/lib/libc/stdlib</filename> then you should either
re-make the world, or at least those parts of it that are re-make the world, or at least those parts of it that are
statically linked (as well as anything else I might have added statically linked (as well as anything else you might have added
that is statically linked).</para> that is statically linked).</para>
<para>At the end of the day, it is your call. You might be happy <para>At the end of the day, it is your call. You might be happy
@ -1383,12 +1381,17 @@ Building everything..
results of that compile to <command>make install</command> on to results of that compile to <command>make install</command> on to
other machines around the network.</para> other machines around the network.</para>
<para>This is not something I have done, so the suggestions below <para>
are either from other people, or deduced from the <warning>
Makefiles.</para> <para>The following suggestions are not well tested or
officially supported; they were derived either from
posts on a mailing list or from the Makefiles. Use
them at your own risk.</para>
</warning>
</para>
<para>The precise approach to take depends on your version of <para>The precise approach to take depends on your version of
FreeBSD</para> FreeBSD.</para>
<para>You must still upgrade <filename>/etc</filename> and <para>You must still upgrade <filename>/etc</filename> and
<filename>/dev</filename> on the target machines after doing <filename>/dev</filename> on the target machines after doing