[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: buildinstall error, is it fatal?



sorry, didn't mean to be cryptic. There may be a more elegant way but I
just hacked mk-images and put a -vx in the shebang line. Lots of output
but you'll know what its doing. From there its an educated guess to
figure out whats taking all the space....

good luck,
Greg


On Mon, 2004-10-04 at 17:35, Mike Honeyfield wrote:
> when you say "I made mk-images be verbose" does that mean there is a
> switch i pass buildinstall or do I edit mk-images?
> 
> Thanks!
> 
> Mike
> 
> 
> On Mon, 04 Oct 2004 17:19:22 -0400, Greg Dickie <greg max-t com> wrote:
> > Ah, thats the trick indeed. I made mk-images be verbose so I could see
> > exactly what it was trying to do and then work backwards....
> > 
> > sorry not much help but I'm pretty sure thats the problem.
> > 
> > Greg
> > 
> > 
> > 
> > 
> > On Mon, 2004-10-04 at 17:12, Mike Honeyfield wrote:
> > > Because I am customise it, but I have not changed the defualt kernal yet.
> > >
> > > If its trying to squeeze too much into the floopy image, how can I
> > > strip it out or find out whats cosuming that space?
> > >
> > > Mike
> > >
> > >
> > > On Mon, 04 Oct 2004 17:01:04 -0400, Greg Dickie <greg max-t com> wrote:
> > > > I believe these messages are coming from the part that tries to make the
> > > > floppy images. Why are you running buildinstall? Did you add some
> > > > drivers or change the kernel? If so they are likely too big to fit in
> > > > the floppy image.
> > > >
> > > > HTH,
> > > > Greg
> > > >
> > > >
> > > >
> > > >
> > > > On Mon, 2004-10-04 at 16:57, Mike Honeyfield wrote:
> > > > > Thanks for the swift reply
> > > > >
> > > > > I have 14Gb of disk space and 386Mb of RAM in this box. My /tmp is
> > > > > almost empty, just some 1k text files.
> > > > >
> > > > > Any other ideas?
> > > > >
> > > > > Mike
> > > > >
> > > > >
> > > > > On Mon, 4 Oct 2004 16:31:50 -0400, David Tegelaar <dtegelaar egenera com> wrote:
> > > > > > Not good but might be an easy fix.  Try clearing
> > > > > > out space in /tmp filesystem.  I've seen these
> > > > > > messages (rarely but it's happened on old Unix
> > > > > > systems) where it really is a lack of memory
> > > > > > causing these messages--not lack of disk space.
> > > > > > Try clearing out /tmp fs disk space though and
> > > > > > hopefully that's all that's needed.
> > > > > >
> > > > > > -dave
> > > > >
> > > > > [snip]
> > > > >
> > > > > _______________________________________________
> > > > > Anaconda-devel-list mailing list
> > > > > Anaconda-devel-list redhat com
> > > > > https://www.redhat.com/mailman/listinfo/anaconda-devel-list
> > > > --
> > > > Greg Dickie
> > > > just a guy
> > > > Maximum Throughput
> > > >
> > > >
> > > 
> > > _______________________________________________
> > 
> > 
> > > Anaconda-devel-list mailing list
> > > Anaconda-devel-list redhat com
> > > https://www.redhat.com/mailman/listinfo/anaconda-devel-list
> > --
> > Greg Dickie
> > just a guy
> > Maximum Throughput
> > 
> >
> 
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list redhat com
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list
-- 
Greg Dickie
just a guy
Maximum Throughput
greg max-t com




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]