From owner-freebsd-questions Fri Mar 13 17:31:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29883 for freebsd-questions-outgoing; Fri, 13 Mar 1998 17:31:08 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29873 for ; Fri, 13 Mar 1998 17:30:46 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id MAA04491; Sat, 14 Mar 1998 12:00:27 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id MAA16487; Sat, 14 Mar 1998 12:00:27 +1030 (CST) (envelope-from grog) Message-ID: <19980314120026.09622@freebie.lemis.com> Date: Sat, 14 Mar 1998 12:00:26 +1030 From: Greg Lehey To: Cory Kempf , Kent Vander Velden , freebsd-questions@FreeBSD.ORG Subject: Re: root filesystem and -current References: ; <199803130024.SAA11363@toybox.cc.iastate.edu>; <199803130024.SAA11363@toybox.cc.iastate.edu> <19980313133514.09198@freebie.lemis.com> <19980314101858.58251@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Cory Kempf on Fri, Mar 13, 1998 at 08:03:06PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 March 1998 at 20:03:06 -0500, Cory Kempf wrote: > 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. Ah, yes, I fear you picked a poor time. Of all the time I've been on -current, that was the greatest volume, one that provoked Jordan to threaten to take people off the list unless they shut up. It's not normally like that, and I reiterate (more quietly this time): If you are running -current, subscribe to the FreeBSD-current mailing list! > 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% Most messages on -current won't directly relate to your immediate problems. But it's the only place to find out what's going on, and you desperately need it. >>>> 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? We're out of sync here. Your original message suggested that you had just built a new -current kernel, and that it would now not boot. What about the previous one? >> 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. Boot: kernel.old Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message