Re: recovering from a failed libc6 upgrade
Hmmm, I see. I guess the kernel from the woody install CD is too old as
well. The lifimages (as suggested in my first mail) have a more recent
kernel however (2.4.19-??). So I guess netbooting is still an option. If you
have an additional machine of course ;)
If you don't have an additional machine, maybe this can help:
http://pateam.esiee.fr/cd-images/testing. These are ISO's with more recent
kernels.
I assume (net)(CD)booting with the latest kernel should solve the chroot
problem.
Tell me if it worked.
----- Original Message -----
From: "Martin-Éric Racine" <q-funk@pp.fishpool.fi>
To: "kenneth westelinck" <kennywest1@hotmail.com>
Cc: <debian-hppa@lists.debian.org>
Sent: Wednesday, November 27, 2002 10:45 PM
Subject: Re: recovering from a failed libc6 upgrade
On Wed, 27 Nov 2002, kenneth westelinck wrote:
> Another solution is to chroot your /mnt. So /mnt actually becomes /.
Unfortunately, that fails right away.
"kernel too old" is the message I get after doing "chroot /mnt", probably
because as soon as the root is changed, we start using binaries living
there,
but they all fail because the wrong libc6 lives there.
--
Martin-Éric Racine
"Kas sa tahad mind? - Nej!!! Är du en idiot?!!"
http://www.pp.fishpool.fi/~q-funk/
Tallinn, Eesti;
Espoo, Suomi.
--
To UNSUBSCRIBE, email to debian-hppa-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Reply to: