atom feed62 messages in org.freebsd.freebsd-stableRe: ATTENTION: Call for opinion re: r...
FromSent OnAttachments
Mike SmithMar 16, 1998 5:33 am 
Ruslan ErmilovMar 16, 1998 6:04 am 
Richard WackerbarthMar 16, 1998 6:31 am 
Satoshi AsamiMar 16, 1998 7:22 am 
Andreas BraukmannMar 16, 1998 7:34 am 
Robert WatsonMar 16, 1998 7:39 am 
ni...@iii.co.ukMar 16, 1998 7:52 am 
Bohdan HorstMar 16, 1998 9:42 am 
John PolstraMar 16, 1998 11:22 am 
Derek FlowersMar 16, 1998 11:47 am 
db...@pelops.comMar 16, 1998 1:12 pm 
Greg ShenautMar 16, 1998 2:06 pm 
Jim HodgesMar 16, 1998 3:20 pm 
Jay NelsonMar 16, 1998 4:42 pm 
StuddedMar 16, 1998 6:49 pm 
allen campbellMar 16, 1998 7:43 pm 
Alexander TatmaniantsMar 17, 1998 2:43 am 
Eivind EklundMar 17, 1998 3:24 am 
Richard WackerbarthMar 17, 1998 5:05 am 
Scot ElliottMar 17, 1998 5:29 am 
Richard WackerbarthMar 17, 1998 6:05 am 
Scot ElliottMar 17, 1998 6:29 am 
Eivind EklundMar 17, 1998 6:38 am 
Richard WackerbarthMar 17, 1998 6:48 am 
Mike BurgettMar 17, 1998 7:15 am 
Burton SampleyMar 17, 1998 7:31 am 
Richard WackerbarthMar 17, 1998 7:34 am 
Gary SchrockMar 17, 1998 10:06 am 
Rodney W. GrimesMar 17, 1998 3:43 pm 
allen campbellMar 17, 1998 6:43 pm 
Michael OskiMar 17, 1998 7:23 pm 
Greg ShenautMar 17, 1998 7:58 pm 
Steve KhooMar 17, 1998 10:28 pm 
Michael OskiMar 17, 1998 10:32 pm 
Matt SaundersMar 18, 1998 2:13 am 
David E. TwetenMar 18, 1998 4:38 am 
Antonio BemficaMar 18, 1998 5:10 am 
Drew Derbyshire - UUPC/extended software supportMar 18, 1998 5:12 am 
Drew Derbyshire - UUPC/extended software supportMar 18, 1998 5:15 am 
zoonieMar 18, 1998 5:45 am 
Mikael KarpbergMar 18, 1998 5:48 am 
johnMar 18, 1998 6:08 am 
John S. DysonMar 18, 1998 6:28 am 
Richard WackerbarthMar 18, 1998 7:15 am 
Richard WackerbarthMar 18, 1998 7:18 am 
Ted SpradleyMar 18, 1998 10:40 am 
Ted SpradleyMar 18, 1998 11:09 am 
Mike SmithMar 18, 1998 12:41 pm 
Mike SmithMar 18, 1998 12:50 pm 
Richard WackerbarthMar 18, 1998 1:09 pm 
Richard WackerbarthMar 18, 1998 1:13 pm 
Mike SmithMar 18, 1998 2:05 pm 
Mike SmithMar 18, 1998 2:32 pm 
Richard WackerbarthMar 18, 1998 3:07 pm 
Drew Derbyshire - UUPC/extended software supportMar 18, 1998 3:33 pm 
Mike SmithMar 18, 1998 3:59 pm 
Mikael KarpbergMar 18, 1998 4:15 pm 
Ted SpradleyMar 18, 1998 5:12 pm 
Richard WackerbarthMar 18, 1998 7:03 pm 
Jay BratcherMar 18, 1998 7:13 pm 
Richard WackerbarthMar 18, 1998 7:58 pm 
sporkMar 18, 1998 11:11 pm 
Subject:Re: ATTENTION: Call for opinion re: root device naming change
From:Scot Elliott (sc@online.barbour-index.co.uk)
Date:Mar 17, 1998 5:29:58 am
List:org.freebsd.freebsd-stable

I've had a few problems witht the new code too. The first couple were caused by my not reading the instructions properly; theese were SCSI devices and I did get it all working OK.

The big problem came when upgrading a system that was origionally a 2.1.5 system with IDE disks. The fstab file had a "wd0a" entry for the root device. I changed this to wd0s1a - which mounts OK on /dist on the 2.2.5-RELEASE system. But when I booted with my new 2.2.6-BETA kernel, it didn't even have a chance to get into single user mode. Just got mesages about "unable to mount root device" - followed by a panic and a reboot. I tried to change the "kernel root on .." entry to wd0s1a - and still the same thing.

So I had to give up and revert to 2.2.5-STABLE.. The machine's miles away so it's kind of hard to test these things. Anyone got any ideas?

Thanks.

Scot.

On Tue, 17 Mar 1998, Richard Wackerbarth wrote:

Date: Tue, 17 Mar 1998 07:06:14 -0600 From: Richard Wackerbarth <rk@dataplex.net> To: Studded <Stud@dal.net> Cc: Mike Smith <mi@smith.net.au>, sta@FreeBSD.ORG Subject: Re: ATTENTION: Call for opinion re: root device naming change

At 8:50 PM -0600 3/16/98, Studded wrote:

Strong vote for keeping it in. In my mind (and with all due respect to those involved) the problems we've seen were caused by too little notice, too little regression testing, and too few people reading the right lists at all. It seems to me that the bugs have been worked out of the thing, and we have an opportunity to shout the news from the

I believe that this is incorrect. I, am I am sure others who might not be so vocal, have a configuration that I don't know how to use with the new kernel.

As I understand it, Mike understands the problem but does not (yet) have a solution short of reformatting the HD.

That said, I did think of another way to handle the problem of a mismatch between a new kernel and an old mount. Put the test for most up to date mount version that someone suggested previously into /usr/sbin/config. If the user is about to do damage, config should bomb loud and ugly with the appropriate information. In fact, this method could be extensible to other cases in the future with a little thought. :)

This is not a version mismatch problem. I have the latest (-stable) of everything. This includes the "mount", MAKEDEV, and kernel changes. All imagined sd0 entries are in /dev, etc.

At a MINIMUM, I think that we need a script which will examine the HD's, the /dev tree and fstab and tell us what to change BEFORE we try to use it.

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message

----------------------------------------------------------------------------- Scot Elliott (sc@poptart.org) | Work: +44 (0)171 7046777 PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019

----------------------------------------------------------------------------- Public key available by finger at: finger sc@poptart.org or at: http://www.poptart.org/pgpkey.html

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message