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 want to retain mint and its grub2 bootloader for now. That would
be accomplished (I believe) by choosing the skip option at
the Install Lilo screen. I'm not entirely sure whether the
grub2 loader on the mint 'side' will automatically pick up slack.
To be sure, would there be any data gathering or other analysis that
I should do when the slack install is finished and before reboot?
thanks
tim
Click here to see the post LQ members have rated as the most helpful post in this thread.
The replies that I am getting is what I had guessed to be the solution.
I appreciate the input and the help.
Thanks of course to trademark91, and
Robert.Thompson - give yourself a pat on the back.
cheers
tim
just update-grub afterwards.
if slackware doesnt start up, you could try adding the following to your grub.cfg, changing what you need to point to your drives/vmlinuz:
Manually editing grub.cfg is discouraged these days on Ubuntu.
I have been triple booting Slackware, XP and Ubuntu for several years, with Ubuntu grub on the MBR
One machine works automatically, but another is a bit awkward to find other OS, so I use a custom grub script file /etc/grub.d/40_custom with the following lines
Code:
menuentry "Slackware Linux (Slackware 13.1)" {
set root=(hd0,7)
linux /vmlinuz root=/dev/sda8 ro vga=normal
}
Manually editing grub.cfg is discouraged these days on Ubuntu.
I have been triple booting Slackware, XP and Ubuntu for several years, with Ubuntu grub on the MBR
One machine works automatically, but another is a bit awkward to find other OS, so I use a custom grub script file /etc/grub.d/40_custom with the following lines
Code:
menuentry "Slackware Linux (Slackware 13.1)" {
set root=(hd0,7)
linux /vmlinuz root=/dev/sda8 ro vga=normal
}
Do NOT run Lilo in Slackware
Thank you for the contribution. I was aware that with grub2, you should be adding custom entries
at /etc/grub.d, but I'm glad that you brought that up. Good tip. And for anyone reading
this, some of the parameters above may be different on your machine.
cheers
tim
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.