Dual Booting 2 Distro in different partition
 

i'm trying to install 2 linux distro on separate partitions. this is my goal of the setup.

hda1 - swap
hda2 - /home
hda3 - /slackware root
hda4 - /suse root

theres two problems that i'm having here first is the lilo.conf. i added the nessasry lines to add the suse partition. i am able to boo the suse partition but it seems that its booting off the kernel settings of slackware. reason why i believe this is that my slackware kernel is 2.6.11.6 while the suse kernel is 2.6.8 and while suse was booting to was indicating the 2.6.11.6 kernel. i want to use the 2.6.8 kernel for suse

my second problem is that i have a separate /home mount point that i was to use for both distro. the only problem is that when setting the /home point on the other distro i get an error saying existing config exist do you want to overwrite. is it possible to have both of the distro to share that /home partition?

thanks!!!

Hello novice26,
As for the /home you might want to try to maybe capitalize your name in one distro and lower case in the other, so you have to different /home/$USER directories. Because it has to store things like app data and Desktop Enviroment/Window Manager data pertaining to each distro, and if you used say KDE in both, it would be confused. So lets say your username is novice26:

use /home/Novice26
and /home/novice26

that's should fix that one, as far as I know.

As for the other boot question, if you post that good old lilo.conf I could see if there is something that I could help with. It just sounds like you are pointing to the wrong kernel image is all.


-onelung

my lilo conf is as shown:
#LILO configuration file
#generated by 'liloconfig'
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
change-rules
reset
vga = 791
image = /boot/vmlinuz-2.6.11.6
root = /dev/hda3
label = slackware
read-only
image = /boot/vmlinuz
root = /dev/hda4
label = suse
readonly

just to note that on hda3 of /boot/vmlinuz-2.6.11.6 i also did a "ln -s vmlinuz-2.6.11.6 vmlinuz" i did that because i was following a guide. the reason why i mention that is because i think my problem is there. i'm not sure how it works regarding boot images but to me the image link is pointing to the same file. for both.

thanks for your reply btw.