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.
Ok I just installed slak 8.1 everything went well, I ran through the whole setup process, installed all the packages I wanted and rebooted, on reboot I get invalid system disk, insert system disk! Ok so before I go through the whole setup process again am I missing some vital step that is preventing me from booting properly? Do I need a boot disk just to start slakware? I recently had RH 7.2 installed on this box, thx for the help
Just noticed - when I boot up, It isnt detecting my Hard drives anymore, so I guess this is the problem. In installing slak what could alter somthing in my BIOS that prevents it from seeing my Hard drives?
tundra -- cool you jets, the kid has a problem.
Just because it happen after he installed Slack, doesn't mean its a Slack problem. This sound like a hardware problem. Check all you cables. Does BOIS see your CD drive? A better forum might in fact be the hardware?
What happens if you try to restart the install process (cdrom or floppy) watch the boot messages . If you have one drive then
/dev/hda will be your harddrive
/dev/hdb will be your CD
I been using Linux for 7 years and never heard of it touching BIOS either
Turns out you you were right, wasn't slak that caused my HD failure, I had my old linux box running for a few weeks, guess this was too much for my ancient HD's. Know I put a new harddrive in and everything works great.
I had this problem when I use to run BSD, however I have changed OS's a few times since then and had no problems, the drives are ancient so I guess it's to be expected. Weird how both times it's happened right before installing a new OS