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 setting up a dual-boot for a friend with Ubuntu Studio and Slackware 13.1. Slackware will be the primary OS and Lilo will control the bootloader. After doing some research it seemed to me the best way would be to chainload grub from the lilo menu, so when I installed Ubuntu I stuck Grub in the Ubuntu root partition instead of the MBR and added the following to Slackware's lilo.conf:
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-18.104.22.168
initrd = /boot/initrd.gz
root = /dev/sda3
label = Linux_Gen
read-only # Partitions should be mounted read-only for checking
other = /dev/sdb2
label = Ubuntu_Studio
# Linux bootable partition config ends
It's not working. It just errors out and asks me to boot something else when I select Ubuntu_Studio from the lilo menu. I've never tried this before so I'm sure I'm making a really basic and stupid error; could somebody tell me what I'm doing wrong?
With Linux Mint I tried to install GRUB on the partition using ReiserFS but I failed. There is some bug in Mint's GRUB so it's also in Ubuntu's GRUB. The only way is to chainload from Ubuntu's GRUB to Slackware's LILO. For comparison Arch's GRUB works well -- it's possible to install it on the partition using ReiserFS.
it seemed to me the best way would be to chainload grub from the lilo menu, so when I installed Ubuntu I stuck Grub in the Ubuntu root partition instead of the MBR
If I were you, I would install grub2 on MBR and then again install lilo and chainload grub2 as primary partition.
For me it worked for FreeBSD bootloaderr and Minix bootloader, who knows it might as well work for you!
Tried piratesmack's solution; still got "error 0x01" or something to that effect. Kapz, I'm not sure I undestand what you're suggesting, can you elaborate? Gnashley... I was hoping to leave lilo in control, but I may have to do what you're suggesting.
Thanks to gnashley I finally solved the problem concerning the installation of GRUB's bootloader at the beginning of the partition using ReiserFS. So I installed Slackware LILO's bootloader at MBR and now I can chainload Linux Mint's GRUB using Slackware's LILO.
To achieve that run the following commands in Ubuntu or Linux Mint:
sudo su -
apt-get remove grub-pc
apt-get install grub
update-grub # answer yes to the question about generating menu.lst
Then run Slackware, add to lilo.conf the following lines:
other = /dev/sda1
label = mint
and run lilo command.
Last edited by w1k0; 12-22-2010 at 05:54 AM.