rc.conf.local error nn7j

Kevin D. Kinsey, DaleCo, S.P. kdk at daleco.biz
Mon Apr 19 13:19:47 PDT 2004

Dan wrote:

>I made an error in the rc.conf.conf file used ;# for rem statement.

Oops!  You can recover, but it may be a tad tricky.

>  It hang on that statement at boot. 

But then it at least gives a loader prompt, apparently?

>Also can't  find shell get error message to use /bin/sh hit  return.

You're being put into "single user mode", and with a read-only
/ partition with no other partitions mounted, most likely.

>  I can't vi the rc.conf.local file vi is not there.

As a result of being forced into single user, some things
have happened.

As mentioned above, /var, /usr, and other filesystems
are not yet mounted.  You'll need to do this by hand.

Your shell resource files are not read, therefore $PATH
is not set.  In order to use most commands, you'll need
to specify the full path.

Try this first:

$/sbin/mount -a

And then just "mount" to see if your file systems were
mounted as if in normal operation.  Sample, your system
may be different, of course:

$ mount
/dev/ad0s1a on / (ufs, local)
devfs on /dev (devfs, local)
/dev/ad0s1e on /usr (ufs, local, soft-updates)
/dev/ad0s1d on /var (ufs, local, soft-updates)

If you can mount your file systems, then you
should be able to call

$/usr/bin/vi /etc/rc.conf

and fix your problem.


Kevin Kinsey

More information about the freebsd-questions mailing list