SuSE 9.1 install over existing Linux partitions possible?

[Dancen]

Right now I've got Windows XP and Slackware 10.0 installed on my computer. I've been using both a decent amount, and I've decided to try out a different Linux distro - namely, SuSE 9.1. I read a lot about installing SuSE and about the LBA issue (which is fine, my drives were all set to that anyway), and figured it should be a pretty straightforward install, but couldn't find the info I was looking for specifically.

What I want to do is install SuSE in the partitions I've already made for Slack. Everything I read about SuSE and its installation said how it would automatically partition from the Windows space and install itself. I can understand it doing this to make it easier for someone uncomfortable with partitioning, but what does it do in my case? I'm not looking to triple-boot (yet), and I'd really just like it to reside in the space I've already set aside and keep my Windows partition intact.

I have actually gone into the SuSE install twice, and both times I got to a point where I hadn't been asked to set anything up and felt like if I clicked "next" it would start doing its own thing, partitioning my drive at its whim. Does anyone know for sure if there is such an "advanced" option later on in the install?

Sorry if this is a bit of a stupid question (like I think it probably is), but I'm still a newb and I don't want to lose everything I've set up in Windows to this point because I was impatient and didn't make 100% sure I was doing the right thing.

Oh, and this is for SuSE 9.1 Personal, installing from CD.

[CaptainPinko]

it's not obvious but in the summary screen try clicking on the underlined words. it is there. Welcome aboard SuSE 9.1, it could be the very last distro you ever need. :)

[CoffeeMan]

I use SuSE 9.1 and I love it. When Partitioning, delete the slack root partition and put the suse one there. Swap will be automatic.

[m3rlin]

All Suse partition are created automatic, if you have Windows XP in another Hard-Drive im not sure if he configures automatic, but i belive there's an option during instalation where you can edit the lilo.conf.

But if you have the Windows XP in the same hard-drive as suse, it's almost sure that he will configure that automatic.

If you install and can't boot windows xp, don't forget if you have windows in primary-secundary IDE

you must add in lilo.conf (windows XP configuration boot)
map-drive = 0x80
to = 0x81

This will make sure that Suse will find Windows XP boot.

Good Luck

[saikee]

I go with coffeeman and expanding a bit further.

If the user doesnot choose automatic install then there is no risk of having WIndows messed up by Suse. Just choose expert mode and instruct Suse to format the Mandrake partition before install itself in it.

I never allow a distro install automatically because I want to exercise my right to choose the bootloader type, the choifce of partition for the distro to be installed, the bootloader location and the invasion of the MBR area.

Automatic installation is for an user who doesn't mind a distro to take over the entire hard disk and doses not realise Suse will occupy no more than 5Gb.

Also Suse will compile all its options including how to use the hard drive and allow the installer to amend these options. The installer has a final say before he/she presses the button to permit Suse to start the implementation. That step may not feature in an automatic installation.

[Dancen]

Thanks for all your replies :)

I went ahead and took that next step, and it turns out there was a lot more configuration I could do with a manual install than I thought. I just went into "change -> partitioning" and did everything from there. The part I thought it would just do its own thing was just the last part of the linuxrc, and "Start Installation" really means "Start YaST." I thought it meant it would go right on and put SuSE on.

I haven't had much chance to play with it yet, I just got it working and I really need to change the video configs and everything. Unfortunately that means installing the ATI Radeon X800 drivers. Right now everything is recognizable, but really messed up. I can't really read text. So that'll take some doing. Well, time to fiddle :D