Ok, I installed Slackware 10.2 alongside my SuSE 10.0 yesterday. I wanted to keep Grub, so I installed LILO to the partition, not MBR. Now I need a way to get to that entry through Grub. How would I go about doing this? I assume so far that it's by adding an entry to grub.conf. I would like to do this preferably through YaST (Boot Loader section).

My SuSE is on hdb4, while Slackware is on hdb1. I selected the bare.i kernel from the Slackware CD on install, because that's the only way it would work out.

If you need the contents of files or more details don't hesitate to ask. I hope to be using Slackware soon.
RedNovember

put this in grup.conf
assuming that hdb is the second hard disk on the system.
Actually if suse and slackware are one the same disk check the suse configuration.

DO you have any cd burners?
If yes since slack by default uses the the 2.4 kernel, in order to burn CD's with Slack, you need to emulate your CD drives as scsi.
SO, assuming hdc and hdd are the CD roms you need something like this in the kernel line:

You won't need lilo at all. Grub can boot slack.

Thanks a bunch mate, I'll reboot and see if this works.
EDIT: No dice, it gives me
It then takes me to a black and blue Grub screen to reselect.

it would be more specific, if you had posted the contents of grub.conf (usually it is here:
/boot/grub/grub.conf)
What you basically do is this:
copy the kernel from slackware (on that partition under /boot ) to the /boot directory on your suse - that is where the suse-kernel is.
This is probably what you missed before and in part responsible for the error you saw in return...
Then add a line like perfect_circle gave here as an example to your suse's grub.conf
(of course the name of the kernel needs to match the actual name of the slackware-kernel
AND the root (hd1,0)statement needs to be the same as the one to boot suse - this would be: root (hd1,3) - but check this...)
This way you don't even need lilo for slackware - just leave it or not - this way done it will just not be used)

Note that--in /boot/grub--it may actually be "menu.lst"

Go here for the ultimate in dual-boot tips: http://www.justlinux.com/forum/showt...hreadid=143973

shouldn't _both_ be there - with menu.lst being a link to grub.conf ?

thanks all - I am booting into Slackware properly. I still can't figure out how to get X running though...

I have menu.lst, but no grub.conf. The error was due to a initrd line that was being passed; removed that from menu.lst and it worked.

No--no need for that.
Never saw it on my Ubuntu system

ok. - Gentoo - which I'm using - uses grub.conf as the default configuration-file.
This is probably done to be somewhat consistent about the naming-sceme for config-files - they are easier identified as such when having this ending (.conf)
This is why in Gentoo menu.lst is symlinked to grub.conf probably.
Grub originally uses menu.lst as its config-file so on other distributions just menu.lst really _needs_ to be there.
I learned something new - Thank you!
I was using lilo until I switched to Gentoo a year ago. That is why I never learned about this.