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.
That change just returned an error: "no such partition"
Earlier someone requested the output of updating grub:
Found linux image: /boot/vmlinuz-2.6.35-30-generic
Found initrd image: /boot/initrd.img-2.6.35-30-generic
Found linux image: /boot/vmlinuz-2.6.35-22-generic
Found initrd image: /boot/initrd.img-2.6.35-22-generic
Found memtest86+ image: /boot/memtest86+.bin
Found Slackware Linux (Slackware 13.37.0) on /dev/sdb1
Nope! That information corresponds to your hard disk slot and is controlled by BIOS thus system takes it as it is. Whereas, partitions are handled by OS and thus they can handle the partition count. Suppose you have got hdd placed on 1st slot then for both OS and BIOS it will be SLOT 0. BIOS do not handle the partition numbering it is completely handled by OS.
Thus, whether it is Ubuntu or any other OS for all of them hdd placed on first slot will be hd0 whereas the partition numbering will depend on bootloader in use.
After fooling around with this for several days a deeper problem surfaced. Basically, I have SATA and PATA drives on different slots on my machine and it's causing conflicts with device names which makes troubleshooting impossible. I think that's at the root of not being able to boot slackware. So I'm putting this on the back burner for now or until I can pick up an extra SATA drive.