According to Kevin Jude: While burning my CPU.
>
> While attempting to install glibc 2.0.7 for star office 5.0, my computer
> flipped out on me, giving an error message which I did not have the
> presence of mind to write down. I could type, but whenever I entered a
Thats is the "fatal" mistake, however i would guess it was something to do
with "linking" the new libs, (if they were installed)
> command (say, ls, or exit) it would give me a message, the gist of which
> was:
> /bin/ls: Command not found
Your old symbolic links to the old libaray versions has been removed but the
new link was not created for some reason, ldconfig got confused and bingo.
> So all I could do was reboot (logging in on other virtual terminals didn't
> help...)
Nope nothing will help, no libs no system.
> Now, when I reboot, it gets as far as the partition check. Here's the
> last bit that comes up on the screen:
>
> Partition check:
> hda: hda1
> hdb: hdb: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> hdb: set_multmode: error=0x04 { DriveStatusError }
> hdb1 hdb2 < hdb5 > hdb3
> VFS: Mounted root (ext2 filesystem) readonly.
This has nothing to do with your problem, its non fatal.
>
> hda1 is my windows 95 partition, hdb1 is my linux partition, and hdb5 is
> a dos partition that I mount when I boot.
> So anyway, when it gets to the last line, it stops. It echos my
> keystrokes, but that;s all the response I get. Does anyone know what I
> did, and how I can fix it?
>
> (And no, I don't have a boot floppy. Why would I ever need a boot floppy?
> :)
Now to solve this problem you need that old bootdisk to access the drive,
when in you must link the libs again with the ln -s command.
I have redhat 4.2 so the libc versions will be different, check the /lib
directory and relink libc.so.5 to libc.so.version number.
In Redhat-4.2 thats..
-rwxr-xr-x 2 root root 21367 Aug 26 1996 ld-linux.so.1
-rwxr-xr-x 2 root root 21367 Aug 26 1996 ld-linux.so.1.7.14
-rwxr-xr-x 2 root root 24580 Aug 26 1996 ld.so
-rwxr-xr-x 2 root root 24580 Aug 26 1996 ld.so.1.7.14
lrwxrwxrwx 1 root root 14 Feb 23 1998 libc.so.5 ->
libc.so.5.3.12
-rwxr-xr-x 1 root root 706960 Apr 9 1997 libc.so.5.3.12
Possably thats not the only link which has been removed, check the readme
file from the archive you were using to update and see if it contains a list
of which libs are affected.
>
> BTW, I'm using Redhat 5.0, and 5.2 is in the mail... I'm planning on just
> hosing my old installation and starting over with a repartitioned hard
> drive, but I would still like to know what's going on here, and if I've
> done any serious damage...
Ah!, well that might be easier for you then, but take heed of what happens
when you try to "half" update a system and something goes wrong and you did
not write down the error message.
No offence but i dont even update libs, i know what can happen, i have been
there and done that, but i do have bootdisks, YES you do need them from time
to time.
>
> TIA
>
> Kevin Jude "As you wave the magic wand...
> North Avenue Nothing happens!"
> Trade School --Castle
>
--
Regards Richard.
[EMAIL PROTECTED]
