SlackwareThis Forum is for the discussion of Slackware Linux.
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'm using LVM over software RAID 1, and I just spent 2 hours trying to recover from the "Please append a correct "root=" boot option" kernel panic after a kernel upgrade.
I thought I would post the solution in case anyone else has a similar problem.
If you run `lilo` and it says something about not being able to boot `non-linear` partitions, then you are having the same problem. It turns out that lilo can't boot to a 'non-linear' partition (AKA a partition with snapshots made of it), which turned out to be the problem. I was making snapshots before the upgrade in case I wanted to revert afterwards. Well, this isn't allowed.
I was able to boot in by hitting TAB during lilo boot-strapping and selecting LinuxOLD as the boot image. Alternatively, you should be able to get a shell using a recover disc.
1. Remove the snapshots (on boot partition and probably root partition, too)
2. Run `lilo` so that it can load the config. If it gives no errors, you should be home free. Restart and see if it works.
Awesome. Now, I don't suppose you could tell me how to switch it over? If it's just simply installing and configuring GRUB I can probably figure it out, but do you have to do something to have it automatically update the bootlist on a kernel upgrade?
I didn't do anything special, but I run Slackware so if and when I ever do a kernel upgrade, it's manual and so is my tinkering with menu.lst. Actually one of my gripes with distros like Ubuntu is that it is so very easy to hose your system with all those frequent kernel upgrades. But I digress. Just install it as usual, there should be a ton of HOWTOs out there. Check out google looking particularly at grub and raid and ubuntu, it might help you not trip over anything. Be careful with the disk numbers according to BIOS and according to grub and according to ubuntu - they can be different.