By default GRUB puts on the 1-st place the system, under which it was installed. So if you reinstall GRUB under Slackware, then Slackware will be #1.

.

Is this the only way to install LILO aside from a fresh install?

Hi,
As I stated earlier you can use as root '/sbin/liloconfig' which will give you the option to run 'expert' or 'simple'. I just always seem to use 'pkgtool' as root.

Hope this helps.
Have fun & enjoy!

As suggested above, if you want to use lilo to do this, open a terminal and log in as root. If you are not root when you run any lilo commands your will get a command not found. As root, you can run either /sbin/liloconfig or simply liloconfig and you wil get the first screen shown in the link I posted above. Just use the down arrow on the keyboard to select the expert option, then make sure the OK is highlighted and hit the Enter key and follow the steps.

The link below has a more detailed explanation of the steps for an expert install of Lilo. It is for an old version of Slackware (9.0) but as far as I can see, the options are the same as for version 14.

http://bamafolks.com/randy/students/...xpertlilo.html

onebuck and yancek:

Thank you I understand now what to do.

The PTSD get's in the way sometimes.

Do you want to keep the drive order as original and grub as the default bootloader? if so, create an entry in /etc/grub.d/40-custom to chainload Slackware or to move the slackware chainload grub entry higher on the menu list, create a /etc/grub.d/05-custom with the slackware chainloader entry. Then change the grub default, and rerun update-grub.

.
If you want to change the boot order where the slackware disk is the first disk and lilo is the default bootloader, then will have to manually boot into the other two distros and reinstall grub and rerun update-grub.

[QUOTE]If I change the boot order to /dev/sdc which is Slackware I get the grub rescue prompt>/QUOTE] you wouldn't happen to be mixing uefi boot with bios boot?

Will installing LILO break Grub in anyway?

No, not if you do it correctly. Given the situation you describe with Slackware on a separate harddrive installing Lilo for Slackware on that drive to the MBR of that drive won't have any effect on Grub on another drive. If you have Grub code in the MBR of the Slackware harddrive, then yes, Lilo will overwrite it. Make sure you get the correct drive.

Got it. I'll take my time and make sure I select the sdc drive that Slackware is on.

After viewing Eric's page I saw that KDE 5 Plasma was added to the current Slackware .iso.
I've downloaded it and will be performing a fresh install of Slackware 14.2.

When I installed Slackware last week it came with KDE 4. I would much rather have KDE 5 Plasma.
http://alien.slackbook.org/blog/tag/kde5/

I was reading this page about confirming location to install LILO. (step 6)

In the example it says:
I do not want LILO to install to the MBR of the first drive /dev/sda.
Instead I want LILO to install to the MBR of /dev/sdc.

Slackware is installed to /dev/sdc.

Would /dev/sdc be correct or is /dev/hdc correct?

/dev/sdc would be correct. /dev/hd* is a relic from older kernels (before the 2.6.19 kernel).

1 members found this post helpful.

Thanks bassmadrigal:-

-::-Now I can proceed.-::-

After a little over 10 days my friend decided that running Slackware was not for him.
So, I didn't have to install LILO.
I've kept the instructions in a file on my system so if need be I can use it in the future.

He decided to go with Voyager X2 HD 14.04 LTS which is based on Xubuntu and Debian.
http://voyagerlive.org/index.php/live-voyager-x2/

My friend says; thank you.