SlackwareThis Forum is for the discussion of Slackware 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.
I'm slowly setting up Slackware 13.1 to replace OpenSuse as my main distro. Suse uses grub legacy as its bootloader, and I'm happy with it and used to using it. Slackbuilds is setup to use grub2, but since it's not compatible with grub legacy, it's not an option.
Right now, if I make any changes to booting either Slackware or Suse, I have to run grub only from Suse to write to the MBR, so my thoughts are to compile grub legacy on Slackware so I can write to the MBR from whichever distro I'm running at the time. I can simply keep identical menu.lst in both Suse and Slackware /boot/grub directories and run the grub.
Is this a good or bad idea? Any caveats? Any better suggestions?
I was a GRUB user from moment I started using Linux. My Slackware install was without any bootloader because I didn't knew that lilo is another one.
However, I use GRUB (legacy) on my main machine and on my Netbook as well. If you use an extra /boot-partition you need to trick a bit, if you want to create a menu.lst with grubconfig. Otherwise I'd recommend to save one on an extra usb device or somewhere else.
Quote:
Is this a good or bad idea? Any caveats? Any better suggestions?
If you're used to use GRUB, take it. It's not a bad idea as long as you get it working.
I used LILO for many years, since I first installed Slackware v1 back in 1994. Since I want to edit the MBR from either distro using the same bootloader, it's either install grub on Slack, or LILO on Suse.
Thanks brianL for pointing out /extra. grub 0.97 even has a SlackBuild script with it. I'm good to go.
Slackbuilds is setup to use grub2, but since it's not compatible with grub legacy, it's not an option.
????.
Your inabilty to make either/both wok with each other is probably a poor basis for such a wide-ranging claim.
As far as I'm concerned grub2 was foisted onto the users unready, but it can be made to work.
????.
Your inabilty to make either/both wok with each other is probably a poor basis for such a wide-ranging claim.
Actually, it's not my inability, it's I haven't even tried making them work together, and probably won't bother to spend the time. From what I've read in my research, there's different syntax for each, so I took that as incompatibility.
I could spend my time making them work together, or I could spend it playing golf....simple choice.
I have been dual booting Ubuntu + Slackware (both 32bit and 64bit Slackware) using Ubuntu's grub2 with no problems at all.
Grub2 uses different configuration files that you need to learn. Otherwise, there is no reason to worry about using grub2 as far as I have experienced.
The advantage of GRUB of GRUB2 is, that Slackware ships GRUB Legacy within /extra. You don't have to download anything, you just have to mount the DVD/CD again, install and configure it.
Distribution: x86_64 Slack 13.37 current : +others
Posts: 459
Rep:
I have five operating systems on two drives,so I have installed GRUB 0.97 on drive 1 and GRUB 0.98 on drive 2... they both do the same job and I can choose between them,I did this so I can learn more of whats going on in the GRUB universe...
I have five operating systems on two drives,so I have installed GRUB 0.97 on drive 1 and GRUB 0.98 on drive 2... they both do the same job and I can choose between them,I did this so I can learn more of whats going on in the GRUB universe...
Errm, thre is no GRUB 0.98. Maybe you mean 1.97, aka GRUB2 ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.