Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I keep getting these. Even once when I tried to list the directory with "ls". "ls" worked directly after that with hardly any pause. I've been trying to compile a 2.6 kernel using gcc-3.4.6 and get segmentation faults at different parts of the build each time.
I finally got drunk and asked someone with more experience than me and he said it could be bad memory. What are the chances of a stick of RAM being bad at certain parts? Is there any way of testing the memory?
If gcc craps out at different stages of the kernel build the
chances of bad ram are > 99% (even though there's a remote chance
of it being DMA related as the stuff gets paged out). I've had
a very nasty case on one athlon machine, where the RAM sticks
were fine in other machines but didn't like this one board for
the heck of it. With memtest they only failed ONE out of all the
subtests, but that was enough to upset Linux (winDOHs ME which
the original owner had been using for yonks never had any problems).
As for the testing: memtest86
It's part of many live CDs.
I am getting the same seg faults while trying to upgrade kernel and I am in the process of testing with memtest 3.2 and got several errors with memory, but not sure if its the cpu cache or the ram. The program is kinda confusing but at lest I know some memory is bad.
Very true that it could be bad memory, but my machine also likes to segfault if I overclock too far, so if you are OC'd, try taking it down and see if the segfaults continue. If they cease, you've gone too far.