Date: Fri, 13 Mar 1998 20:03:06 -0500 From: Cory Kempf <ckempf@enigami.com> To: Greg Lehey <grog@lemis.com>, Kent Vander Velden <graphix@toybox.cc.iastate.edu>, freebsd-questions@FreeBSD.ORG Subject: Re: root filesystem and -current Message-ID: <v04003a13b12f8002d3ad@[208.140.182.45]> In-Reply-To: <19980314101858.58251@freebie.lemis.com> References: <v04003a0ab12f0521f376@[208.140.182.45]>; from Cory Kempf on Fri, Mar 13, 1998 at 10:50:10AM -0500 <199803130024.SAA11363@toybox.cc.iastate.edu>; <199803130024.SAA11363@toybox.cc.iastate.edu> <19980313133514.09198@freebie.lemis.com> <v04003a0ab12f0521f376@[208.140.182.45]>
next in thread | previous in thread | raw e-mail | index | archive | help
At 18:48 -0500 98.03.13, Greg Lehey wrote:
>On Fri, 13 March 1998 at 10:50:10 -0500, Cory Kempf wrote:
>> At 22:05 -0500 98.03.12, Greg Lehey wrote:
>>> On Thu, 12 March 1998 at 18:24:28 -0600, Kent Vander Velden wrote:
>>> The big one: IF YOU ARE RUNNING -CURRENT, SUBSCRIBE TO THE
>>> FREEBSD-CURRENT MAILING LIST!
>>
>> Tried that. Signal was rather low, noise was way too high.
>
>You're the first person to say that.
I was on that list for a total of 24 hours, between the 3rd and 4th of
March. I signed on to that and several other lists at the same time.
In that time, there were 121 postings. As near as I can tell, without
reading all, but based on subject lines and a random sampling, 112 of those
were on the subject of raising money. Noise, IMO, and rather loud. The
merits of that discussion is a side issue.
The other 9 looked to be technical, but had not related to the problems
with system. Even counting those postings as signal (they weren't for me,
but I assume they were for someone), that is a ratio of 0.08%
>>> What has happened is relatively complicated: they've eliminated the
>>> "compatibility slice", so you will no longer be able to mount
>>> /dev/sd0a. Use /dev/sd0s1a instead (in /etc/fstab). Don't be put off
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>> by the fact that it will then claim to mount /dev/sd0s2a; that's a
>>> known bug.
>>
>> Tried that.
>
>What did you do?
What you said: "Use /dev/sd0s1a instead (in /etc/fstab)."
Changed the entry in /etc/fstab for / from /dev/sd0a to /dev/sd0s1a.
Reboot.
>> Still Panics on boot.
>
>What's the panic?
I will forward my prior postings. The rest of the list probably doesn't
need the reruns.
>> Putting it back via a fixit floppy after root refused to mount
>> because it had the wrong device in /etc/fstab was real fun.
>
>You don't need that. Just boot the old kernel.
Considering that the kernel hadn't changed, that would be a neat trick.
Unless there is another way to edit files on / when / won't mount?
> He didn't know how to recover from the problem.
Considering that I did recover, and in fairly short order, I would say that
I did understand how to do so. But hey, I am always willing to learn: mess
up your /etc/fstab file, reboot, and recover. Then tell me an easier way
to do so that via the fixit floppy.
+C
--
Thinking of purchasing RAM from the Chip Merchant? Please read this first:
<http://www.enigami.com/~ckempf/chipmerchant.html>;
Cory Kempf Macintosh / Unix Consulting & Software Development
ckempf@enigami.com <http://www.enigami.com/~ckempf/>;
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v04003a13b12f8002d3ad>