Re: recovering from a failed libc6 upgrade
Well, my solution is about the same. Except you're using the Woody CD, I'm
using the images from the ESIEE people to perform a netinstall. It's about
the same.
There's probably an option in apt-get to tell it where to put the libc6
(something like a prefix). Dunno the option, sorry.
Another solution is to chroot your /mnt. So /mnt actually becomes /. After
that, just mount your CD rom, add it to your sources.list and install the
working libc6 from the CD. Instead of installing the libc6 from CD, you
might want to compile a 2.4.19 kernel, which is also possible in your
chrooted environment. I do this all the time when my system gets broken
after an apt-get upgrade.
Hope this helps.
----- Original Message -----
From: "Martin-Éric Racine" <q-funk@pp.fishpool.fi>
To: "kenneth westelinck" <kennywest1@hotmail.com>
Cc: <debian-hppa@lists.debian.org>
Sent: Tuesday, November 26, 2002 4:53 PM
Subject: Re: recovering from a failed libc6 upgrade
On Tue, 26 Nov 2002, kenneth westelinck wrote:
> What about netbooting a lif image from the ESIEE people?
> http://pateam.esiee.fr/cd-images/lifimages
> - exit the installation
> - mount your local disk
> - chroot to the disk
> - install/compile newer kernel
> Should work ;)
Come again? :)
Booting from the Woody install CD, in rescue mode, was my first reaction.
However, when booting in that mode, init is executed right away. Since just
about everything in Debian depends upon a working libc6, that fails.
My second idea was to boot the CD in install mode, but only execute the
keyboard
selection step at the begining, then switch immediately to console and mount
the
/ partition of my boot disk to /mnt. Great, except, how do I install the
libc6
that came on the install CD, over the failed new one that's on the
hard-disk?
--
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: