Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 have debian installed and yesterday I installed slackware 10.1. I use lilo via the MBR. Both the /boot partitions with the kernel images are on the distro's root partition. The problem is now that I for either distro I get the kernel from the distro with which I last run lilo. I solved this now by simply copying the sources and use the same kernel but that's not an option for the long run as I'll probably use slackware to test things out while keeping my debian as stable work environment.
Example slackware 2.4 kernel debian 2.6. I run lilo in debian and get the 2.6 kernel in slack. When I run lilo in slack I get the 2.4 kernel in debian. This is my lilo.conf file:
Originally posted by syg00 Why do you reckon you have to re-run the lilo command every time you update your kernel (normally situation I mean) ???.
Cause it will have the wrong image in the lilo.conf file otherwise. IIRC "make install" runs lilo itself but that either didn't copy the image to the place I want or it didn't set the right one in lilo so I have to manually do that.
I looked at a grub menu.lst file. So if I say (don't have the proper syntax) root device is hdbx it will get the /boot folder on that root device? Do I never have to rerun grub as in lilo?
Simplest solution in my opinion is to run lilo only in one distribution. I have a similar setup (with two versions of RedHat) and only run lilo in RH8.
If I need a new lilo configuration (never do, but OK), I load RH8, update lilo.conf in RH8 and next run lilo in RH8. RH8 is, BTW, the default OS, which makes it simpler to remember.
So if you need a second kernel for slack (newer version) for testing, build it in slack, boot into debian and modify the lilo.conf for an additional slack entry with the new kernel and activate it in Debian by running lilo..
Do you have a seperate /boot partition or not? Are those distros on the same hard disk? If you don't have a seperate partition for /boot and both distros on the same hard disk could you post that part of your lilo.conf file?
Well the problem is that it won't do that solution. Basically the lilo configuration I posted above should do that but I get the debian kernel. The kernel is there in /dev/hdb7 /boot folder but I simply get my debian kernel like this. How do I edit it so that it'll work or does grub work completely different and doesn't have this problem.
Originally posted by darkleaf I looked at a grub menu.lst file. So if I say (don't have the proper syntax) root device is hdbx it will get the /boot folder on that root device? Do I never have to rerun grub as in lilo?
The root(hdx,y) specifies the location of /boot mountpoint - generally the location of the kernel, and grub stage files. The latter will be (hdx,y)/grub/*.* - which resolves in Linux terms to /boot/grub/*.*
I seem to be making this harder than it is.
The upshot is that you *NEVER* have to rerun grub unless you need to re-install it.
Was the major reason I dropped lilo years ago - I was using NT4 ntldr, and got sick of continually copying the lilo boot sector record over to NT after running a lilo command. Well actually I used to keep forgetting, and the Linux boot would fail - THEN I'd remember.
In your case, compile the kernels and copy to /boot as a unique name - create an entry in /boot/grub/menu.lst (generally symlink'd to grub.conf), and away you go. My current conf has 6 Gentoo entries in it - I can pick any one at any time.
Do I have to keep all the kernel images in one folder /boot (as in making a new partition for that) if I do that with 2 distros (I understand how it works with one distro at one hd but with more kernels) or isn't that necesarry and can I keep the slackware kernel on the slackware partition and the debian kernel on the debian partition?
You shouldn't be running two LILO's. Choose either Slack or Debian to be your "master" distro and have the active LILO there. It's easiest to use the original LILO, the one that was there first.
Let's say you have Debian as the "master". Using Debian, make a directory "slackware" under /mnt and then make an entry in Debian /etc/fstab for the Slack partition with "/dev/hdb7" and "/mnt/slackware" in it, along with the other usual stuff for fstab entries.
Still in Debian, edit the slack section of lilo.conf:
Mount the Slack partition manually and then run "lilo" as root (otherwise you'll get an error for the Slack partition)
Then disable (rename) the Slack lilo.conf so you'll only have the one (Debian) active lilo.conf. You can add as many distro's as you want like this, just skip the "install bootloader" step for each distro and edit your Debian lilo.conf accordingly