can't reboot after messing up my rc.conf file

Loren M. Lang lorenl at
Sun Feb 20 14:49:16 GMT 2005

On Thu, Feb 17, 2005 at 12:44:55AM -0800, Sandy Rutherford wrote:
> >>>>> On Wed, 16 Feb 2005 20:02:02 -0600, 
> >>>>> Jamie Novak <novak at> said:
>  > I may have missed something from the thread before I joined the list,
>  > but is there any reason you can't just mount the filesystems and use vi
>  > as you're used to? If you're getting far enough in the boot process to
>  > get an opportunity to interact with a shell, you should just be able to
>  > mount -a and vi whatever. (Or, if you want to play it safe (or if the
>  > system wasn't cleanly shutdown before), fsck and then mount -a)
> This should work fine. Although, depending on where he is in the boot
> process, / may be mounted read-only.  Do `mount -uw /' to make it
> read-write.
> The lesson here is that when editing any file that is even remotely
> connected to the boot process, _make_a_backup_copy_.  You can then
> simply mv the backup copy back into place should you mess up.

Actually, Absolute BSD has a handy suggestion about using rcs for all
important files in /etc/.  Maybe you should try looking into that.

> Sandy
> _______________________________________________
> freebsd-questions at mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at"

I sense much NT in you.
NT leads to Bluescreen.
Bluescreen leads to downtime.
Downtime leads to suffering.
NT is the path to the darkside.
Powerful Unix is.

Public Key:
Fingerprint: B3B9 D669 69C9 09EC 1BCD  835A FAF3 7A46 E4A3 280C

More information about the freebsd-questions mailing list