Do not want lilo in my MBR, want to use System Commander to boot
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Do not want lilo in my MBR, want to use System Commander to boot
I have a dual boot box, W98 and Linux V7.1
I do not want lilo in my MBR. Instead, I want the System Commander boot loader there, so I can boot either windows or linux or System Commander. I cannot, at this time add a linux selection to my System Commander Boot Selection Menu that works. I keep getting messages telling me that I have an invalid MBR.
Here is my lilo.conf:
boot=/dev/hde
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux
I think that, in order to be able to boot linux from my System Commander Boot Selection Menu, that I have to change something in lilo.conf to cause lilo to go into my "root superblock:, however, I am not sure what the "root superblock" is. Also, I have recompiled my Kernel and am calling my new kernel "mykernel" as opposed to the old one, "vmlinuz".
Here is my HD setup:[list=1][*]hde1 is Windows[*]hde2 was created automatically at the very start of my HD, and is where the lilo bootstuff is. [*]hde3 is another windows partion[*]hde5 is linux regular stuff (programs and data)[*]hdf1 is linux swap (don't ask me why, linux put the swap partition on hdf to my amazement).[/list=1]
So as not to make too much work for anyone who wants to help me with this, I understand that, in order to boot into "mykernel", I have to change the "default" entry, and add another stanza reflecting the stuff related to "mykernel".
So, my questions are:[list=1][*]What do I change in my lilo.conf to make lilo install to my "root superblock:"?[*]Do I have to toggle anything to get System Commander to start linux?[/list=1]
You can install lilo into the boot sector of the root partition by changing the line boot=/dev/hde to boot=/dev/hde5 . As for your new kernel, you can add an entry for it and keep your old kernel in case something happens. Your lilo.conf would look like this:
boot=/dev/hde5
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux
I've never used System Commander, but my TurboLinux distro came with a special version. In the manual it says that if linux doesn't appear in the OS selection menu, then press ALT-S and select the Order, add, and removal menu. Next, press ALT-A and then select Partition. You should see a listing of all your partitions. Then select your linux root partition and press ALT-T to make it bootable. Press ESC until you reach the OS selection menu. Linux should be there. Hopefully. I hope this helps.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.