MEPISThis forum is for the discussion of MEPIS Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Windows 98 on hda1
Mepis on hda5(SWAP), hda6(root), and hda7(home)
DamnSmallLinux on hda8
(I plan to install other distributions later for comparison and experimentation.)
Windows was installed first. Mepis came later with GRUB boot loader installed and 'menu.lst' in the '/root/grub' directory. Finally I loaded DamnSmallLinux which, I believe, installed the LILO boot loader with its 'lilo.conf' file in '/etc'.
With those entries(see exerpts below) in 'lilo.conf' I can boot DamnSmallLinux(default) and Windows, but when I try to boot Mepis I get:
Mepis
GRUB
and the system hangs. Because both Windows and DamnSmallLinux boot and work properly, I assume something changed with Mepis when I installed DamnSmallLinux.
I have to 'CTRL-ALT-DEL' to regain control.
Here are pertinent entries from my 'lilo.conf' file:
--- beginning ---
boot=/dev/hda
# Specifies the device that should be mounted as root. (`/')
I'm not sure how you screwed this up, but obviously lilo is not configured correctly. Here is how I would fix this. Boot with Mepis CD, login as root, go to Mepis OSCenter and reinstall grub to the MBR of hda. Restart computer to make sure you can get WinXP and Mepis.
Then, in Mepis su to root and edit /boot/grub/menu.lst and add at bottom:
title DamnSmall
chainloader (hd0,X)+1
(Assume you have only one hard drive.... hda = hd0. Grub uses a one-less-then number scheme... no letters, and all drives are 'h' and not 's' like in Linux of sata.... PITA :-))
Pay attention to this:
X = one less than the partition number where Damn is installed. So '3' would be the partition 4 if that is where you put it. How do you know? Go to KDE - InfoCenter ---> Partitions and you can see the partition numbers (/dev/hda3 .... in which case you use '2' in grub.)
Next, reinstall Damn Small and instruct it to put grub or lilo (prefer grub) NOT on the MBR but on the 'root' or 'boot' partition or something similar. Again NOT the MBR.
Reboot machine. Grub should come up and give you choices. If you pick DamnSmall grub sees the chainloader command and goes to the partiton and executes whateve boot-loader is there... and that is that.
When I installed Mepis grub was installed on hda6, and for DamnSmallLinux lilo was installed on hda8 as stated. As far as I know, nothing was installed on the MBR. I wanted Mepis and DamnSmallLinux to be treated the same, i.e. simple distributions.
Now I don't understand the reasoning behind installing grub for Mepis in the MBR but grub(or lilo) for DamnSmallLinux on hda8! There must be something I don't fully understand. Why should the distributions be handled differently?
Does the fact that I'm using Windows 98 instead of Windows XP make a difference?
Distribution: antiX using herbstluftwm, fluxbox, IceWM and jwm.
Posts: 631
Rep:
Firstly. PITA is Pain In The Ass
Secondly, where you put your grub/lilo boot loader doesn't make any difference to how your distros work. All it does is choose which boot loading screen you will get to choose from. But you need to install one in the MBR otherwise you won't be able to dual/triple boot (actually there is another way, but it is even more complicated)
I would suggest you follow a.canton's advice; it won't affect how windoze, Mepis nor DSL works. They will be treated the same.
You must have a boot loader on the MBR. M$ XP puts one there so it can boot.
You install Linuix and you replace the MS one with a Linux one.... either grub or lilo. A bootloader is told where to look for its instructions. When you installed Meips it loaded grub on the MBR and programmed it to look for all of its instructions on the Meips partiton in /boot/grub/menu.lst.
OK, so the grub starts up and reads menu.lst which puts up a screen for you to choose either XP or Mepis.
Now here comes the interesting part. You want to install DamnSmall. DamnSmall will recognize the XP partition. If Damn is smart it will recognize the Mepis partition.... but my bet is that it won't. Thus you would install grub all over again on MBR... and it would look for menu.lst in the Damn Small partition. You could not boot Meips since there is no entry in menu.lst on Damn for it... since it does not know about Mepis (only Windows XP). You COULD put an enrty in the menu.lst on DamnSmall IF you knew what to write. (If you are a grub expert you would!)
BUT... since you already had grub installed from Mepis on the MBR and it knew where to look for the menu.lst (in Mepis) I see no reason to re-install grub when you pop in Damn Small. Leave it there! When you install Damn Small tell it to put its boot loader in its OWN root partition... NOT the MBR. So now you have 2 loaders... one on the MBR which is read by BIOS and one hidden away in the DamnSmall partition.
All you have to do is make an entry in the Mepis menu.lst using the 'chainloader(x,y)+1 notation. It simply says to grub: "You can stop now and go to hard disk partition Y and whatever loader you find there, start it up." That's what "chainloader" means. It means to 'chain' to a second loader.
So when you boot up, the BIOS reads the MBR and runs grub which puts up a menu on the screen. If you pick Mepis, all is well and Mepis starts. If you pick DamnSmall, grub 'branches' to DamnSmall partition and runs its grub (or lillo) and you get another menu with whatever option DamnSmall wrote in IT'S menu.lst.
Yeah there is more overhead but it can make it easier to maintain as most folks have one MAIN distro they use all the time (Mepis) and one they are testing out (DamnSmall, Kanotix, etc.). If you don't like Damn Small you dump it and you don't have to worry about the bootloader on the MBR pointing to a menu.lst it can't find so long as Mepis is always there. Of course if you delete Mepis then you can't boot to DamnSmall. But as I say, most folks don't dump their 'regualr' distro.
So with my method you are executing TWO boot loaders and it takes a few more seconds but it works well. Not only that but DamnSmall will pop up a menu and you can enter cheatcodes if you like. I like to have each distro on my HD have its own bootloader. It works for me... but others like a different method. All I know is that when I have a bootloader on the MBR that works... I don't want to mess with it or delete it and reinstall a new one (unless I'm dumpting the distro it is pointing to, obviously)
Linux is all about choice and there is no wrong way.
I know I didn't diagnoise or solve your problem. No time for that. I'm telling you how I do it and that it works for me. The choice is up to you to follow it or do it some other way.
Hooray!! Well almost. Thanks to you two. I can finally boot any of three systems - Windows 98, Mepis, and DamnSmallLinux. Most of my configurations were lost or changed, but now I know a way to conveniently add distributions. I've got to make sure a new distribution does mess with the MBR though!
DamnSmallLinux had installed itself in the MBR. I still don't know why that wouldn't work.
Originally posted by bigoli anticapitalista and acanton:
DamnSmallLinux had installed itself in the MBR. I still don't know why that wouldn't work.
Thanks again..
Didn't Damnsmall give you a choice of WHERE to install the boot loader... or not install one at all? Most distros offer to install on MBR or their own root parttion.
How did it get on the MBR?
What did you do next? Reinstall Mepis or did you 'fix' the menu.lst of Damnsmall?
Set up a box last week with a dual boot system.
I used GAG for that one, my first use of GAG.
It's a Graphical Boot Manager, it installs into the MBR.
Most impressed, lots of options and doesn't need or use a partition.
GAG can be installed/repaired from either floppy or Boot-CD.
Assign a password for each partition, also set a password for the boot-administrator.
Easy to set up and repair mangled MBR resulting from "that last OS install".
Read the doc's included in the down loaded program.
That took longer than doing the job because I read them 3 times.
>Didn't Damnsmall give you a choice of WHERE to install the boot loader... or not install one at all? Most >distros offer to install on MBR or their own root parttion.
It gave me the option to run 'mkliloboot' or something like that. I don't recall if it told me it would lilo though!
>What did you do next? Reinstall Mepis or did you 'fix' the menu.lst of Damnsmall?
I reinstalled GRUB using the MEPIS LiveCD and added an entry for DamnSmallLinux.. See post.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
