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.
I may be a newbie to Linux, but I have been working with, and programming computers since the mainframe days, and the days where the Commodore 64 was considered awesome, yet I enrolled in a Computer Science degree at an Australian uni (starting next year) and the uni recommends I become familiar with Unix/Linux. So I tried Debian, but spent days trying to resolve dependencies using Deselect, and finally admitted defeat. Then I bought an Australian Linux magazine that had RedHat 9 on 4 CD's. After 4 or 5 installs, and much aquired knowledge, I am now left with a Linux partition that wont boot - msg is "Kernel panic: no init". Of course, this is the end of it. I have had loads of different problems over the last 2 months, including "Id "x" respawning too fast. Disabled for 5 minutes.", and errors trying to start gnome/kde - X-windows, inability to login at times at run-level 3, my Linux boot hanging at "Starting xfs:", fsck repeatedly finding corruption, "Segmentation faults", "broken pipe errors", and the list of problems goes on.
I have a simple question (that probably doesn't have a simple answer): can anyone with experience with Linux tell me - how is it that a system in state "A", left in state "A" when rebooted, seems to change into state "B", not as a result of user changes or input, but somehow the system itself changes. In other words, I can have a fully healthy running system at 1.00pm, then, rebooting, I can have a system that will not boot by 2.00pm, and by 2.15pm my filesystem will not mount, and yet I have done nothing to change it! Linux may be a great system, and considered more stable than any Windows OS, yet it is great when I can actually use it, and of course it is stable when I am able to use it (i mean it is stable and functioning 2 days out of 6), which, by definition defeats what is meant by stable; yet this trusty and reliable system is currently down on my computer, all the while the so-called "troublesome" Windows is happily running here on my computer and has been fully functioning over the last 2 months while my RedHat system has been crashing.
Don't get me wrong. I want to use Linux, and I know enough to know that it has great potential. I wouldn't be spending time in these forums if I didn't. I just want its promise of a multi-threaded, multi-user and fully customizable system to be fulfilled. I just want to know why my RedHat 9.0 system keeps crashing, or failing when I do nothing to change it. It just seems to want to destroy itself of its own accord.
Could it have anything to do with the fact that I am running Windows XP on hda1, and Linux (root) on hda5 - i.e a dual boot system?
It seems you've been quite unlucky indeed. Sometimes problems like this can happen when the system is not 100% stable... usually bad memory or something, possibly from an overclocked machine.
Even if things appear to be stable in Windows, I find Linux pushes the hardware more and so hardware problems can seem more 'loud'. It's possible many small things could snowball...
Of course maybe you just have some kind of unique hardware combination that is causing magical errors... If this is the case then trying many new distros is probably a good option - some might have kernel patches that address driver bugs.
I'm also from Australia and currently in a Computer Science degree (at Macquarie Uni). Which uni are you going to? And did they mention Linux specifically? (that's pretty cool if they did )
Distribution: Lots of distros in the past, now Linux Mint
Okay, I had a similar problem waaaaaaaay back when I was starting. Most of it was just me, so perhaps this doesn't help much. Still, maybe it will.
Okay, first problem. Windows works fine, Linux flips out. Open case. Dust bunnies over memory chips, courtesy of whatever bonehead installed the cooling fan/heatsink so that the draft was blown directly onto them.
Second problem. Using the wrong kernel. I know that sounds incredibly ignorant, but I got a giveaway computer from a friend, and he said it was an AMD, and I installed the AMD kernel. Only thing was, it was an Intel cpu. Lots of problems, but nothing solid. Just lots of errors all over the place.
Another guess, and this is wild-arsed as hell, but perhaps there's a problem with your partitioning? Redhat 9, as far as I know, doesn't repartition NTFS drives (XP). Mandrake 9.1 does, reportedly. If you resized you drive with redhat, and it wasn't able to do that properly, that might be part of the problem.
Honestly, I don't know, but I know that your problems are extremely unusual. If it's not the partitioning, I'd run a good hardware test (especially on the drive) to make sure it wasn't a hardware problem. And if it is the drive, I'd make backups in a hurry.
Thanks all for taking time out with your suggestions.
Salparadise - thanks for the tip on Mandrake, I have also heard it is good and relatively trouble free.. I may well look for that distro soon...
Miknight - I have enrolled in a Comp. Science degree at Uni of New England (U.N.E) in Armidale (North West NSW)... they have encouraged me to become familiar with unix/linux, I believe their system for Computer students is a version of Linux. I thought it would be good to become familiar with Linux, I know they use the Unix OS as the OS they study when we delve into Operating Systems in 2nd and 3rd year... I don't start until 1st semester next year, and am still debating whether to stick with Comp. Science or do a Physics/maths degree instead (I am wondering whether I have the right temperment to do computers full time..!)
Further updates on my problem - it is highly likely that my problems are hardware related.. Windows XP crashed last night with a blue screen doing a physical memory dump.. it is not the first time this has happened, but I thought that because it hadn't happened since i shelved my internal modem, that my problems were over.. looks like not. I also have lost 3 other HDD's in the last 18 months.. tech support here advised me to try and upgrade the following:
Better power supply
Basically, I have had numerous HDD failures, and lately bsod with a physical memory dump (along with all the Linux trouble)
If anyone here has any suggestions on how to identify what component(s), given my troubles, are likely at fault, feel free to give me your advice.
you might want to find some way of testing your RAM
there are diagnostic apps, i know of one in particular, PC. Doctor, it's a win app. It does a series of tests on whatever device you specify and I have had some success with it in the past.
I dont know if there's a linux equal (would be interested to know)
i've only pseronally experienced bsod's under xp when there's been memory with problems
either due to bus speed problems or incompatibility at some level
have you changed or upgraded the memory recently?
try different memory
or if there's more than one strip
try one then another
i have had similar problems in only one system and it was a faulty ram chip. i finally replaced it and every problem just disappeared. i am pretty sure random issues are hardware issues. windows will crash now and then. linux will just wont work
Originally posted by salparadise I dont know if there's a linux equal (would be interested to know)
Memtest86 is probably the best memory testing program in existence. You download the image of the program and write it to a floppy disk, and then boot off the floppy to run the tests (when you think about it, that's the only way to get reliable results).
The image can be written to the floppy from Windows or Linux (or whatever). It's also licensed under the GPL