Date: Mon, 19 Apr 2004 15:18:49 -0500 From: "Kevin D. Kinsey, DaleCo, S.P." <kdk@daleco.biz> To: Dan <longterm@chatusa.com> Cc: freebsd-questions@freebsd.org Subject: Re: rc.conf.local error nn7j Message-ID: <40843429.60604@daleco.biz> In-Reply-To: <00c101c42629$a580c1d0$ca89ded1@dannewxp> References: <00c101c42629$a580c1d0$ca89ded1@dannewxp>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40843429.60604>