AuthorTopic: Unexpected dual boot behavior (Read 2446 times)

I'm dual booting Slack and Vector. But I ran into a little unforeseen situation.

The way I have it set up right now, Vector works perfectly. Slackware (clean reinstall after Vector) on the other hand does boot, but on the Vector kernel . So that gives some errors, although the system does work, with some unexpected behavior. Also, the Vector bootsplash is displayed at boot when booting Slackware

Can the above be easily adjusted to get dual boot working? it goes without saying that I want the Slack entry to boot the /boot/vmlinuz on /dev/hda4. But as it seems it boots the same named one on /dev/hda1. It might be very simple - or I might be very simple - but I'm just not seeing the logic behind it.

OK, thnx! That's another interesting solution. I'll give it some thought. Don't know if it'll be of use to me right now though, as I'm already thinking to overwrite Slack with Mandriva to study the inner workings of Metisse. I've tried, and failed, to install Metisse over Slack a while back. Being able to compare two distro's side by side may improve my chance of success ;-)

Everyone is always talking about Beryl and Compiz, but I'm really impressed with Metisse.

OK, thnx! That's another interesting solution. I'll give it some thought. Don't know if it'll be of use to me right now though, as I'm already thinking to overwrite Slack with Mandriva to study the inner workings of Metisse. I've tried, and failed, to install Metisse over Slack a while back. Being able to compare two distro's side by side may improve my chance of success ;-)

Everyone is always talking about Beryl and Compiz, but I'm really impressed with Metisse.