On Wed, 2005-04-27 at 08:16 +0100, mike wrote:
> On Tue, 2005-04-26 at 09:08 +0100, mike wrote:
> > On Mon, 2005-04-25 at 10:15 -0400, Peter Jones wrote:
> > > On Mon, 2005-04-25 at 14:23 +0100, mike wrote:
> > > > On Mon, 2005-04-25 at 07:36 -0400, Alan Cox wrote:
> > > > > On Mon, Apr 25, 2005 at 09:35:16AM +0100, mike wrote:
> > > > > > When I try to install test2 on my home machine (an amd k6) the install
> > > > > > always exits with a fatal error when it tries to install glibc-common.
> > > > >
> > > > > If you look at the other consoles during this are there errors reported
> > > > > about CD bad blocks ?
> > > > >
> > > >
> > > > will check when I get home, but if this was the case, surely I would get
> > > > a retry prompt, not a fatal error?
> > >
> > > Well, depends on where the failure was and what it was. Show us the
> > > error message when you get a chance? ;)
> >
> > the only messages are on tty1
> >
> > rpmdb /var/lib/rpm/--db.001:unable to initialise environment lock:
> > Function not implemented
> >
> > on tty5
> >
> > spurious interrupt on irq7 (had this on successful installs)
> >
>
> anyone any ideas on this?
So are you saying there's not actually an error reported? What does
anaconda actually say as it goes bye-bye?
--
Peter