Skip to Content.
Sympa Menu

sm-grimoire - Re: [SM-Grimoire]heeeeellllpppp!!

sm-grimoire AT lists.ibiblio.org

Subject: Discussion of Spells and Grimoire items

List archive

Chronological Thread  
  • From: Andrew <afrayedknot AT thefrayedknot.armory.com>
  • To: Grimoire <sm-grimoire AT lists.ibiblio.org>
  • Subject: Re: [SM-Grimoire]heeeeellllpppp!!
  • Date: Thu, 14 Nov 2002 11:06:48 -0800

dont panic.
ive seen this before. It happens because ld-2.2.5.so (or other version
number) gets trampled on by the build. This magic file is what loads all
elf executables, if it, or its symlink to ld-linux.so.2 gets trampled,
then you get that error. This happened to my housemates computer, and
it sucks.

enough explaining. here is how to fix it:
from the rescue iso, mount your source mage root partition (say on
/mnt/stuff) copy over ld-2.2.5.so into /mnt/stuff/lib, then make sure
there is a symlink to ld-linux.so.2. After that, you should be ok. To
check try chrooting into /mnt/stuff/lib. If it works, you are good to
reboot, if not then you must have missed something.

once you are able to chroot back into your root partition, you can go
ahead and reboot. The trick i always pull to make sure glibc doesnt hang
itself is this:
mkdir /tmp/lib
cp -vp /lib/* /tmp/lib (ignore errors)
vi /etc/ld.so.conf (add a line at the end for /tmp/lib)
ldconfig (this will complain, but who cares).

at this point you have a spare copy of ld in your tmp directory. No
matter what glibc does, it has a backup ld for you. After the cast is
successful (and your circuit breaker doesnt die during the make install
(mine did once)), you should be ready to go with the new glibc. After
that I hold gcc and glibc, and do a sorcery rebuild. Once that finishes,
I go ahead and delete my backup /tmp/lib, and the line in ld.so.conf.

perhaps BUILD for glibc should do this, just to be safe?

Andrew
On Thu, Nov 14, 2002 at 11:25:42PM +0800, Craig Dyke wrote:
> Seem to have caused myself a problem and seem to be stuck to fix it :((
>
> I was trying to do a rebuild when all of a sudden lots errors started to fly
> up the screen about "no such /bin/blah" where blah could be 'ls' or 'grep'
> or any other executable.
>
> Thinking (<== this may be too strong a word) that if I reboot all may right
> itself I now have a kernel panic saying that I have no 'init' which I
> presume is the same problem with the excutables :((((((
>
> Any suggestions would be greatly appreciated :))
> (Perhaps a quick reply also might not be too much to ask for [he asks
> sheepishly])
>
> Craig
>
> The not so wise
>
>
>
> _______________________________________________
> SM-Grimoire mailing list
> SM-Grimoire AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-grimoire




Archive powered by MHonArc 2.6.24.

Top of Page