On Thu, 2005-06-09 at 20:58 -0500, Randy McMurchy wrote: > Since updating Glibc is usually not > recommended, this means the original headers used on the system > during the initial system build (when Glibc was built) should > never be touched.
OK, that makes sense. It also reminds me of my first Linux system, installed the week after I bought a new PC and had plenty of room to play with multiple boot partitions. I went right to redhat.com and downloaded the latest install (on a *dialup* connection), and amazingly managed to get a working system going in a few hours despite the fact that I never bothered to read a single book or website on the subject. All went well until I got the urge to start tinkering. I wanted to install something or other that was too bleeding-edge for my kernel and gcc, and in no time I was in dependency hell. Download the new version of the library this program required and the library needed a newer gcc. Downloaded the RPMs for the newest gcc and it needed the new glibc. Downloaded the RPMs for the newest glibc... and that's when things got bad. RPM pointed out that I couldn't upgrade glibc because glibc was in use. So I tried to rpm -u (uninstall) glibc, which of course wouldn't work because ten thousand things depended on it. Not to let a stupid error message get the best of me, I read the man page for rpm and learned how you could force an uninstall and ignore dependency warnings, so I used that option and finally had my way - I forcibly removed glibc from my working Red Hat system. Needless to say, I no longer had a bootable system any more. Let me tell you from personal experience, the shell and associated core utilities get really angry with you if you remove glibc while they are running. That was about 5 years ago. I like to think I'm a bit smarter now, but I know that's just an illusion. Hey, what does this rm -rf / command do? -- Peter B. Steiger Cheyenne, WY -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
