Add a question which has come up a few times on -questions recently. ("How

can I fix a syntax error in rc.conf which causes the root filesystem to be
read only?", or something to that effect.)
This commit is contained in:
Ben Smithurst 2000-08-25 18:37:39 +00:00
parent bc7dd81816
commit b97ae5dc7e
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=7898
2 changed files with 68 additions and 2 deletions
en_US.ISO8859-1/books/faq
en_US.ISO_8859-1/books/faq

View file

@ -15,7 +15,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.87 2000/08/05 16:41:45 ben Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.88 2000/08/14 17:40:22 ben Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries
@ -4328,6 +4328,39 @@ future:</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I made a mistake in <filename>rc.conf</filename>, and
now I can't edit it because the filesystem is read-only.
What should I do?</para>
</question>
<answer>
<para>When you get the prompt to enter the shell
pathname, simply press <literal>ENTER</literal>, and run
<command>mount /</command> to re-mount the root filesystem
in read/write mode. You may also need to run <command>mount
-a -t ufs</command> to mount the filesystem where your
favourite editor is defined. If your favourite editor is on
a network filesystem, you will need to either configure the
network manually before you can mount network filesystems,
or use an editor which resides on a local filesystem, such
as &man.ed.1;.</para>
<para>If you intend to use a full screen editor such
as &man.vi.1; or &man.emacs.1;, you may also need to
run <command>export TERM=cons25</command> so that these
editors can load the correct data from the &man.termcap.5;
database.</para>
<para>Once you have performed these steps, you can edit
<filename>/etc/rc.conf</filename> as you usually would
to fix the syntax error. The error message displayed
immediately after the kernel boot messages should tell you
the number of the line in the file which is at fault.</para>
</answer>
</qandaentry>
<qandaentry><question>
<para>How do I mount a secondary DOS partition?</para></question><answer>

View file

@ -15,7 +15,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.87 2000/08/05 16:41:45 ben Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.88 2000/08/14 17:40:22 ben Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries
@ -4328,6 +4328,39 @@ future:</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I made a mistake in <filename>rc.conf</filename>, and
now I can't edit it because the filesystem is read-only.
What should I do?</para>
</question>
<answer>
<para>When you get the prompt to enter the shell
pathname, simply press <literal>ENTER</literal>, and run
<command>mount /</command> to re-mount the root filesystem
in read/write mode. You may also need to run <command>mount
-a -t ufs</command> to mount the filesystem where your
favourite editor is defined. If your favourite editor is on
a network filesystem, you will need to either configure the
network manually before you can mount network filesystems,
or use an editor which resides on a local filesystem, such
as &man.ed.1;.</para>
<para>If you intend to use a full screen editor such
as &man.vi.1; or &man.emacs.1;, you may also need to
run <command>export TERM=cons25</command> so that these
editors can load the correct data from the &man.termcap.5;
database.</para>
<para>Once you have performed these steps, you can edit
<filename>/etc/rc.conf</filename> as you usually would
to fix the syntax error. The error message displayed
immediately after the kernel boot messages should tell you
the number of the line in the file which is at fault.</para>
</answer>
</qandaentry>
<qandaentry><question>
<para>How do I mount a secondary DOS partition?</para></question><answer>