Date: Thu, 17 Feb 2005 00:44:55 -0800 From: Sandy Rutherford <sandy@krvarr.bc.ca> To: Jamie Novak <novak@qwest.net> Cc: freebsd-questions@freebsd.org Subject: Re: can't reboot after messing up my rc.conf file Message-ID: <16916.22919.40934.655595@szamoca.krvarr.bc.ca> In-Reply-To: <20050217020202.GB34810@mail.oss.uswest.net> References: <03fb01c51457$3f246ff0$0b01a8c0@enigmedia.net> <1108595484.708.8.camel@chaucer.jeays.ca> <4213F7A1.3030304@cis.strath.ac.uk> <20050217020202.GB34810@mail.oss.uswest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> On Wed, 16 Feb 2005 20:02:02 -0600, >>>>> Jamie Novak <novak@qwest.net> 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. Sandy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16916.22919.40934.655595>