On Sun, 25 Nov 2001, Osamu Aoki wrote:
> On Sun, Nov 25, 2001 at 01:22:57PM +0100, A.R. (Tom) Peters wrote:
> > I think this is what happenend to my system. I tried to install
> > whatever was the current g77 compiler. It required libc6-2.2.4-5; I had a
> > lower version, which got replaced. But this broke (ba)sh, version 2.05-8,
> > which depends on libc6-2.2.3-7 or higher. This breaks everything,
> > including apt and dpkg, which spawn shells all the time.
> Wow this is a mess. (I do not see similar problem though. I upgraded
> last night) Did you do
> # apt-get update
> # apt-get install bash
> Or just used dpkg -i bash... ?
I didn't upgrade bash. I tried install the g77 compiler. That had libc
upgraded, which appeared incompatible with whatever version of bash
happened to be on my system. Then the package installation scripts
wouldn't work anymore. System severely broken.
> > Upgrading bash first will not help, because it will not work with the old
> > libc6; c.q. the new libc6 will be installed first anyway because the
> > new bash depends on it; but then the upgrade process crashes because the
> > old bash doesn't work with the new bash...
> Latest bash on testing/unstable are 2.05a-2 and
> Depends: base-files (>= 2.1.12)
> Pre-Depends: libc6 (>= 2.1.2), libncurses5
> So should not be a problem.
> > I would appreciate if someone e-mail me a libc6-2.2.3-7.so (naked i386
> > binary, NO .deb package - or tell me how to extract the binary from a
> > .deb) - hoping that just replacing the damn thing will save me.
> You still have old debs at /var/cache/apt/archives? Then you can
> extract it with "ar" command or "dpkg" command.
I haven't, but note that `dpkg` doesn't work anymore because is spawns
shells, which do not work anymore.
> But to me easiest fix is to install a new bash from testing.
Yeah, but how to get it?
I was lucky that I had a CD with some old binary of bash that happens to
work with the newer libc.
> In either case it may be easiest to have small 2nd system installed on
> your hard disk as 2nd Linux system (or have some 2ndary shell like sash
> installed on your system) for system recovery. I usually have 2nd linux
> system as dual boot. I can mount broken system to /target and
> install needed packages with "dpkg -root /target -i package.deb"
> from functioning system.
>
> If you still have somewhat functioning system, why not update/upgrade
> through apt-get? If bash segfaults, use sash, ash, pdksh... It may
> work.
sash does not work at all as a replacement for bash (apparently it is
really interactive and doesn't do well in running the init sh
scripts). ash appears somewhat better but gets into trouble later in the
init process.
--
#>!$!%(@^%#%*(&([EMAIL
PROTECTED]@^$##*#@&(%)@**$!(&!^(#((#&%!)%*@)(&$($$%(@#)&*!^$)[EMAIL PROTECTED]@)
Tom "thriving on chaos" Peters
NL-1062 KD nr 149 tel. +31-204080204
Amsterdam e-mail [EMAIL PROTECTED]
