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

Do some minor language cleanup and suggest that people also back up

Browse source 
their modules directory, and change it to be "we" instead of "I", and
while I'm at it rearrange the runon sentence that made this whole
question actively painful to read.
This commit is contained in:
Michael Lucas 2001-12-19 21:45:14 +00:00
parent 9a12ab0ac8
commit acead78ae5
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=11466
1 changed files with 10 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -5465,15 +5465,17 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
kernel config section of the Handbook</ulink>.</para> kernel config section of the Handbook</ulink>.</para>
<note> <note>
<para>It is recommended that you make a dated snapshot <para>We recommend that you make a dated snapshot
of your kernel of your new <filename>/kernel</filename>
in <filename>kernel.YYMMDD</filename> after you get it all called <filename>/kernel.YYMMDD</filename> after you get it
working, that way if you do something dire the next time working properly. Also back up your new
you play with your configuration you can boot that kernel <filename>/modules</filename> directory to <filename>/modules.YYMMDD</filename>. That way, if you make a mistake the next time
instead of having to go all the way back to you play with your configuration you can boot the backup kernel
instead of having to fall back to
<filename>kernel.GENERIC</filename>. This is particularly <filename>kernel.GENERIC</filename>. This is particularly
important if you are now booting off a controller that is not important if you are now booting off of a controller that
supported in the GENERIC kernel.</para> GENERIC does not
support.</para>
</note> </note>
</answer> </answer>
</qandaentry> </qandaentry>