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.
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.
I'm using suse 10 and ubuntu 8.10 in my Laptop. Just before a day, I updated suse which changed the Kernel file names. Now I get file not found in the grub while loading suse. However, when i mention the path (hdd0,2) to Kernel file, it loads without any issue.
The boot flag is with sda3. But, when the computer starts, it directly goes to sda7 and reads the menu.lst available in sda7 (ubuntu). If I make any changes in the sda7, it reflects in the booting time. but the changes made to the /boot/grub/menu.lst available in sda3 is not working.
Can anybody explain how the grub skips sda3 and moves to sda7 when the boot flag is with sda3...
I expect that you installed Ubuntu after Opensuse and the Ubuntu Grub installed its stage1 file to the master boot record pointing to the remaining Grub bootloader files on the Ubuntu partition (sda7). As syg00 said, boot flag is irrelevant for Grub.
If you want Grub to use the menu.lst in your sda3 partition, you have to reinstall Grub to the MBR so that it points to that partition; you can do that with (as root user):
You people are exactly right. The boot flag is irrelevant for the grub. I confirmed by moving the complete /boot (sda3) files to another folder and checked. The computer restarted and entered in to ubuntu /boot (sda7). Therefore, I concluded that the changes are in MBR and not in the /sda3 partition.
Thanks for every ones effort in replying. have a great day.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.