Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
This morning my system wouldn't boot into Slackware. Actually I went into the partition from Mandrake and configured it to boot to console instead of X and it will do that but it won't run X. The reason /var/log/XFree86.0.log is gone, along with other files from that directory. Now I didn't delete them so I don't know what happened. My footing with Linux isn't that great yet. The solution as I see it is a reinstall but is there a command something like DOS's undelete that I can run from console to try to dig the files up from their graves? I'd prefer to figure out what went wrong and why so I can learn from this instead of doing a straight reinstall but I'm not sure where to start.
hda9 and hda11 are my Mandrake partitions, which I made accessible to Slack because Mandrake wouldn't install properly and I wanted access to all of the files from Slackware to help hunt down the problem. Everything else is pretty standard I'd say. I made the Mandrake partitions accessible days before I had the problem, I don't think that they are the cause of the trouble.
And finally, the result of df -h:
When I'm running the commands I pipe the results to a text file on my 98 data drive so I can then post them up on the web from 98 but I've noticed that the error portions don't get included in the text file, they appear on the screen. Is that normal? shouldn't all of the information, error or no, be piped into the text file?
I don't have any reason to suspect my attempts to fix my bad Mandrake install are the cause of the problem, there's too much time between the last "tweak" i attempted and the first appearance of this problem, but I'm going to try to undo the last few things I did just in case. In the mean time if anyone else has any idea's I'm listening.
Originally posted by OC_eobard When I'm running the commands I pipe the results to a text file on my 98 data drive so I can then post them up on the web from 98 but I've noticed that the error portions don't get included in the text file, they appear on the screen. Is that normal? shouldn't all of the information, error or no, be piped into the text file?
That's actually a good clue - it means the parts you don't see are being issued as errors rather than as output.
When you pipe the output of a program it only sends the parts that are written to STDOUT (standard out) to the pipe; if you're seeing things onscreen that aren't being sent to the pipe then they are most likely being sent to STDERR (standard error). Both STDOUT and STDERR are printed to the screen when you run commands at the command line.
So one question (at least) is, what would give your errors like
when you use the 'ls' command?
Are you using any command aliases? Have you changed the standard path?
All of the specific files listed in the errors above give me another error:
chmod: failed to get attributes of 'var/log/(whatever)': Permission denied
I'd almost think it was my hard drive going on me but 98 performs rock solid and Mandrake is just as good as ever (which isn't saying much but at least the specific problems I've been having with Drake have remained consistent)
Does Mandrake know how to handle reiserfs format? Could booting to Drake and then doing something as simple as reading the directory (which is reiserfs) from Mandrake (which I installed on an ext3 format partition) cack something up? Mandrake only gave me the option of ext2 or ext3 when I installed, if reiserfs wasn't on the list then it seems possible it was because the version of Mandrake I have (9.2) wasn't 100% compatible with it. If so could something as simple as listing the directory contents from console (or Konqueror in X) damage the system?
^Ok I was going to post that, but then I booted to Drake and ran diskdrake and it can tell the difference between ext3 and reiserfs, so I'm assuming that Mandrake knows the difference, but I'm not sure if Mandrake is 100% compatible so I figured I should post it just incase I'm on to something. I'm taking shots in the dark at this point. Still gonna keep trying though....
It sounds like you have something corrupted in the filesystem.
That should reboot the system with a forced fsck check. If it's still messed up after that you may want to to rename /var/log to something else and then make a new /var/log. You may have to drop to runlevel 1 to do that.
Forcing fsck didn't change anything. Got a link to a detailed explanation of the steps I'll need to go through to rebuild /var/log? I know how to change the runlevel, but I'd like to look at all of the stages I'd need to go through and why.