I don't think my problem is the same that you were having... My setup is
as follows, i have a 2.6 GB WD as hda my CD-Rom drive as hdb and a Seagate
240 MB drive as hdc.  Could the problem be that i have hdc as my /tmp dir,
and the rest of my install on the Western Digital drive (hda) ?  It's not
that this is really a life threatening thing, i just prefer to have the
xrpm thingey, rather than the console based 'rpm -i' deal.  Should i maybe
just scrap the install again, and start fresh?  I'm in a quandry.  

John Roberts
 
   ***********************************************************************
   *"Bonjour, ya cheese-eatin' surrender monkeys!" - Groundskeeper Willie*
   ***********************************************************************


On Tue, 25 Aug 1998, Gevaerts Frank wrote:

> 
> 
> On Tue, 25 Aug 1998, Stephen Newey wrote:
> 
> > I'm not sure if this is your answer, but I've had similar problems
> > before on certain hardware, if the there's a gap in the IDE chain, i.e.
> > you've got hda as your hard disk and hdc as you CDROM, Linux can
> > sometimes have trouble accessing it properly. Try taking out the gap
> > between devices by putting the CD-ROM as hdb, I'm new at this so I'm not
> > sure if it's the answer or not. And this is posted from Outlook because
> > I'm from work.
> 
> Are you sure ? I never heard about that being a problem.
> 
> Frank
> > 
> > Stephen.
> > 
> > > I have already done that, i was trying to install from both the
> > > directories on a CD-ROM (/mnt/cdrom/blah/blah) and my /tmp dir.  And
> > > the
> > > bar did not move either time.  So i have to use the 'rpm -i
> > > package.rpm'
> > > method.  Could there be another explanation?  Does it matter that my
> > > /tmp
> > > dir is physically a different hard drive than the rest of my linux
> > > install?  
> > > 
> > > John Roberts
> > > 
> > > 
> > > **********************************************************************
> > > *
> > >    *"Bonjour, ya cheese-eatin' surrender monkeys!" - Groundskeeper
> > > Willie*
> > > 
> > > **********************************************************************
> > > *
> > >  
> > >  
> > 
> 

Reply via email to