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.
Here as the past week or two my /bin files keep corrupting, along with some others. If I replace them with backups they work fine, for about a minute and then they SegFault again. I've also noticed that is happens when I switch back between Xwin and console.
I've even started with a fresh install of slackware, yet it just did the same thing. ls -al will list the amount of files, and then segfault for example. It's getting nervewrecking. I'm running kernel 2.4.31. Any insight?
You may want to
- check your filesystem
- check your free disk space (when some of your hd partitions are full, this may cause weird effects)
- check your harddisc (hardware)
- check your cable connections (plugged tightly enough? correct orientation? correct order?)
- check your file system access rights
- check your swap partition
- check your termination if it is a SCSI disk
- check your SCSI IDs if it is a SCSI disk
- check your SCSI partition mapping if it is a SCSI disk
Looks like there's a lot of things to check, but most of them don't take a lot of effort or time.
I'm running ext2 filesystem. However, it's ONLY the /bin files that corrupt. This laptop is only 3 months old, I don't imagine the hard drive would be bad already. I've ran e2fsck on the drive, and it shows no bad blocks. My swap partition is fine. All the drives are IDE.
The files stay just fine until I switch over to Xwindows. When I do that, they start segfaulting. They file size is also increased, and that has me suspicious. Strace has showed nothing that meant anything useful to me.
Has anyone had these problems due to Gnome? I'm really trying to figure it out, and it has me baffled. It is related to Xwindows somehow. The second I sudo a program or su to root to do something, it causes SegFaults and my files become larger. Doesn't make sense to me.