rc.conf.local error nn7j

[Dan]

I made an error in the rc.conf.conf file used ;# for rem statement.  It hang on that 
statement at boot. Also can't  find shell get error message to use /bin/sh hit  
return.  I can't vi the rc.conf.local file vi is not there.

Dan
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: rc.conf.local error nn7j

[Matthew Seaman]

On Mon, Apr 19, 2004 at 06:08:22AM -, Dan wrote:
 I made an error in the rc.conf.conf file used ;# for rem statement.  It hang on that 
 statement at boot. Also can't  find shell get error message to use /bin/sh hit  
 return.  I can't vi the rc.conf.local file vi is not there.
 

Right -- you've rebooted, and your system can't come up properly, so
is dumping you into single user mode.

The fix is pretty simple though.  Hit return to get a shell prompt.
Now type:

# fsck -p
# mount -a

then edit the rc.conf file:

# vi /etc/rc.conf

and finally:

# reboot

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgp0.pgp
Description: PGP signature

Re: rc.conf.local error nn7j

[Kevin D. Kinsey, DaleCo, S.P.]

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.

Dan
 

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.

HTH,

Kevin Kinsey
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]