Here is a tip related to general segmentation faults when various software begins to show them.
Background of box, The box I have installed Slack on is a corporate throw-away. It had a P2 233 mhz-2.5gb-64mb-pc66. I upgraded it to a 350mhz-3.5gb-256mb-pc100/133 pushing slightly faster than 370mhz.
I have had Slack for 2 months now and have tweaked, installed and uninstalled lots.. In the past few days I had been experiencing segmentation faults with various software, trouble rebooting, occational freezes. I googled and read various forums about this issue.... There is a wide band of answers about this subject rangeing from being cracked to mega hardware failure. What was a girl to do??

Seems the majority listed hardware over software troubles with a re-install included... So with nothing to lose I began work... Seeing how the system had got to a really bad point...

First don't panic.....
Second hack your hardware first.

I hacked my box, replaced the cmos battery, rearranged the ram, un-overclocked it.... Well that made my problem worse....
Ok pulled the first ram and replaced it with a new one. Still a problem. No boot hda or cd-segmentation faults. Pulled the second ram and replaced it with a new one.... TADA all is well. The system staiblized and is back to speed. Doing slighty better than 390mhz.

What are you getting at here????
This- Don't panic. Chances are you have a hardware issue and if you are running Linux or BSD chances are you are a hardware hacker as well as software hacker. Check your hardware first.... Then your OS. RAM old or new can easily be bad. As a box builder I see it all the time.

My hobby is building throw-away boxes (older) that many people think no one wants. I get them free, test them, tear them down-rebuild-upgrade and sell them as internet devices to people who just want to have a computer for the net but cannot afford a high-end system or does not know much about computers but has a desire to learn them. My service to my community....