SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
A tip on segmentation faults, general.
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....