On Monday 13 May 2002 00:52, Lonnie Borntreger wrote:
I tried to upgrade from glibc 2.2.4 to 2.2.5. Upon rebooting I got a
whole bunch of dma read failures on my disk (ext3) right after I got the
message that it was starting init. Obviously this made so that none of
the filesystems got
On 13 May 2002 00:52:39 -0500
Lonnie Borntreger [EMAIL PROTECTED] wrote:
I tried to upgrade from glibc 2.2.4 to 2.2.5. Upon rebooting I got a
whole bunch of dma read failures on my disk (ext3) right after I got the
message that it was starting init. Obviously this made so that none of
the
On Mon, 2002-05-13 at 05:27, Marcel Pol wrote:
On 13 May 2002 00:52:39 -0500
Lonnie Borntreger [EMAIL PROTECTED] wrote:
I tried to upgrade from glibc 2.2.4 to 2.2.5. Upon rebooting I got a
whole bunch of dma read failures on my disk (ext3) right after I got the
message that it was
I tried to upgrade from glibc 2.2.4 to 2.2.5. Upon rebooting I got a
whole bunch of dma read failures on my disk (ext3) right after I got the
message that it was starting init. Obviously this made so that none of
the filesystems got mounted, and none of the init scripts ran.
Downgrading again
Hello all...
Any trick to upgrade glibc and not have to spend hours and hours resolving
dependencies? and without using rpmdrake or MandrakeUpdate???
Thanks
On Friday 10 November 2000 23:02, you wrote:
Hello all...
Any trick to upgrade glibc and not have to spend hours and hours resolving
dependencies? and without using rpmdrake or MandrakeUpdate???
Thanks
Download and install db1, db2 db3 from Cooker, and after that
glibc.
Regards,
Yo,
On Fri, Nov 10, 2000 at 05:02:25PM -0500, Patrick Poncet wrote:
Hello all...
Any trick to upgrade glibc and not have to spend hours and hours resolving
dependencies? and without using rpmdrake or MandrakeUpdate???
AFAIK, when you upgrade glibc it will be compatible, so no problems
