Re: what to do when libc6 upgrade goes bad
Sarel Botha wrote:
>
> > Having updated libc6, I didn't know whether a reboot was in order, since
> > that is a fairly important library for just about everything. Well,
> > this was a bad idea, since my machine hung rebooting, and then nothing
> > would run once the kernel finished starting. Couldn't log in, rescue
> > disk doesn't have dpkg, and I was sorta stuck, and sort of frantic
> > (moreso, in fact).
>
> It wasn't necessary to reboot...
>
> Couldn't imoprtant binaries that could stop a machine from rebooting be statically linked to avoid problems like this ?
Well, I am not sure about that. Once I installed the new libc6, it
didn't seem that dpkg was installing things properly anymore (again, I
was installing guile 1.3, so the other stuff installed was libncurses,
slib, libguile, and of course, guile itself). I didn't have any
experience with this, so I brushed it off as dependency problems of some
sort.
As for static linking, it would have been nice if the rescue disk could
have had dpkg on it so that I could mount my CD and re-install the older
libs, but it actually wasn't that bad afterall... definitely a learning
experience.
-dh
Reply to: