Messages in this thread | | | Date | Sat, 2 Aug 1997 07:42:05 -0700 (PDT) | From | Blu3Viper <> | Subject | Re: 2.1.48-2 upgrading libc's... |
| |
On Sat, 2 Aug 1997, linux kernel account wrote: > I was attempting to upgrade libc's on one of my two 4.1.48-2 test > computers (This was on my uniprocessor one), and It crashed and burned.. > Yes, I understand that upgrading libc's on a live system is dangerous.. > but I've done it several times before.. > > Anyways, I was untarring the new libc on top of the old one and ever > interactive program hung.. Daemons keept going (sshd, smbd), but
This has been the case for as long as I can remember. Never overwrite a running libc. mv it to another filename, and then untar your libc.
I was first bitten by this two years ago ;)
david.
[reply to: david@127-0-0-1.kalifornia.com without the 127-0-0-1.] *** *** Flames will go to /dev/null ** WARNING ** SPAM mail will be returned to you at a *** *** minimum rate of 50,000 copies per email
| |