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 am very new to not just linux but especially to slackware. I finally made it through the install and when I go to reboot for the first time the screen just prints "01 01 01" over and over, and nothing else happens. I am completly stumped about the whole process. I tried to run setup again and reconfigure slackware, but to no avail. Any help is greatly appreciated I am dieing to dive into slackware!
Did you use lilo as your boot manager? I'm not sure but I remember ages ago I had lilo as my boot manager and I screwed up my partitions majorly and that's what I got when I turned on my machine. I fixed it with fdisk /mbr because back then I still ran Windows which saved my ass.
What was the sitation on the box before the install
of Slack? Previous lilo-installs from a different distro?
If I remember right (I've never used the default) Slack
installs to the installations root partition ... thus the
message you see can't be from Slack's lilo if you
followed all defaults ... to resolve the issue boot with
the 2nd slack CD (select the partition where you
installed to) and edit your /etc/lilo.conf
Where is says something like
boot = /dev/hdx1
change it to your first hdd without a number,
boot = /dev/hda
Boot the 2nd CD again, and at the console you have the recovery version of Linux up so you need to access the Linux installed on your hard drive. You should know the partition you installed Slackware onto (such as root is in /dev/hda2) and you can mount that partition into the rescue CD's tree: mkdir /mnt/hd mount /dev/hda2 /mnt/hd
Then you can edit the lilo.conf from there (vi /mnt/hd/etc/lilo.conf) and change the line to boot = /dev/hda. After editing the file, you can optionally wipe the current MBR with: dd if=/dev/zero of=/dev/hda bs=512 count=1
But make sure you type that in correctly, especially with the count=1 or it starts to wipe your whole hard drive! Whether you chose to wipe the current MBR or not, getting lilo on the MBR should be as easy as typing: lilo -C /mnt/hd/etc/lilo.conf
or if for some reason lilo isn't on the rescue CD: /mnt/hd/sbin/lilo -C /mnt/hd/etc/lilo.conf