[SOLVED] Grub/ Grub2/ Lilo - canīt install any of them properly!
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.
EricFl is right
I never use a /boot partition...never really understood why anyone does..
but I think thats the issue
Usually the reason is because the Linux root file system is encrypted and can't be accessed by GRUB. The file system for "/boot" has to be unencrypted. Creating a "/boot" mount point makes the directory layout look normal. I believe I may have also seen some distros use the extra symbolic link that I mentioned in my previous (edited) post.
Except for my painful experience installing Linux on fake hardware RAID I wouldn't have learned a lot about GRUB booting. I have to say that the painful experience was with Slackware 10. At that time Slackware was the only distro that I could figure out how to boot from my RAID. Today, Slackware is much easier to install on fake hardware RAID. Slackware has made exceptional progress in adding flexibility and support for unusual boot requirements.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Well, I tried removing the /boot section of the menu.lst line as suggested. Completely forked it up. Kernel panic ensued, and it also somehow stopped my USB boot stick from working so I can't get into my slack installation at all.
I dug out an old super grub disk from somewhere and that can't boot it either. I'm in puppy linux at the moment trying to get back into slackware to sort something out - i will try to put in the extra simlink as you suggest.
I hate Grub with a passion, I have as little to do with it as possible, and i'm remembering why again.
Additional - I created the simlink, tried to boot again, still kernel panic. Error message says something about not syncing - unable to find init.
now, I suggest you make or get a compatible slackware livecd/usb to fix anything if it ever gets messy again. Better than using Puppy or some other non-slack distro!
That's why I made the MiniSC and MiniSCR, runs just like Slax
their slackware -current but I have one that has both the slackware 188.8.131.52-smp kernel and a 184.108.40.206 kernel too. the latest one only has 220.127.116.11-smp kernel
MiniSCR (R= rescue) (best for persistent usb) http://multidistro.com/NFLUXNEW/SQ4/...os/miniscr.zip
I also think that the separate boot-partition might be the issue. I recently installed Slackware 13.1 and created a separate boot-partition (for information, the reason for this is that on older PCs, but maybe not anymore, be BIOS (?) couldn't handle boot partitions larger than X mb so it was recommended to create a boot-partition which was smaller than 1 GB/1024MB).
I couldn't get it to boot, so I tried installing with everything on the same partition, and then it worked.
For my installation I had lilo as boot manager though as that was the default.
A Salix USB would make a handy backup certainly, i'll give that a go.
You are probably right that the boot partition is the problem, but I normally use one as I normally encrypt mobile devices. I only didn't bother this time as I was in a hurry and there doesn't seem to be an easy way to encrypt with the Slackware installer - I intend to reinstall Slackware on this lappy soon but using encrypted LVM.
Hopefully it will be easier next time now I know more about how grub works and I will definately have a Salix USB rescue installation!
Grub2 uses grub-mkconfig to generate a configuration file for you. It appears to work fairly well, although I've written a /etc/grub.d/09_slackware_linux file (based off the 10_linux file that comes with the grub2 slackbuild) that attempts to match the way Slackware does things versus (I guess) Debian's way.
I've got a mix of SATA and SCSI drives, a root partition on lvm, a separate /boot ext2 partition and a Windows XP drive. grub-mkconfig managed to find everything and provided valid menu entries. (Well, the 10_linux menu generator script appears to believe that you would use an available initrd with any kernel that has the same version number.)