[SOLVED] dual boot Slack-win7

Hi everyone. I'm aware that slack 14.2-x64 use gpt partition table, while win7 doens't support it. I wonder if I could get dual boot installing win7 firstly under mbr, then installing slack switching to gpt. Thanks a lot.

This thread from Ubuntu's website looks like a good place to start: https://askubuntu.com/questions/7847...ws-10-with-gpt

Originally Posted by frankbell This thread from Ubuntu's website looks like a good place to start: https://askubuntu.com/questions/7847...ws-10-with-gpt

Thanks for the answer. Sorry I didn't mention dual boot would be with only one hard drive, so will use just gpt. This is not the case of that guy. I'm still with the doubt.

I am not sure about whether Windows 7 lacks support for GPT, but Slackware can be installed on MBR partitions no problem, if that would be acceptable to you. I never looked into GPT myself and for dual booting always stuck with a simple partitioning scheme: /dev/sda1 for Windows C: (after partitioning, install that first), /dev/sda2 for Slackware /boot, /dev/sda3 for swap, /dev/sda4 for Slackware root (/).

Originally Posted by heyjann I am not sure about whether Windows 7 lacks support for GPT, but Slackware can be installed on MBR partitions no problem, if that would be acceptable to you. I never looked into GPT myself and for dual booting always stuck with a simple partitioning scheme: /dev/sda1 for Windows C: (after partitioning, install that first), /dev/sda2 for Slackware /boot, /dev/sda3 for swap, /dev/sda4 for Slackware root (/).

I don't know if w7 lacks support for GPT, but it indeed don't let me install over it.

Yes! MBR is acceptable for me, but slack's installer force me to create a GPT partition table. I will search for slack-14.2_x64 over MBR on google.

EDIT: are you sure slack-14.2_x64 can be installed on MBR partition table?

The installer itself does not have any partitioning tools I think, one has to use cfdisk or fdisk.

https://docs.slackware.com/slackware...l#partitioning

I will admit I am unfamiliar enough with gpt that I just double-checked cfdisk to see if I am not accidentally using it, but it says label:dos instead of label:gpt for my drive so I'm really on MBR.
And Slackware works fine here.

Most Linux livecds come with partitioning tools I think, you don't necessarily have to prepare your drive with the Slackware disk.

This is anecdotal evidence that Slackware 14.2 installs fine on DOS/MBR type drives:
https://www.youtube.com/watch?v=s1gGwsegfrU

There is a corresponding one for GPT drives, it seems more complicated to me, four partitions? :
https://www.youtube.com/watch?v=2dGc-LIiOTQ

Originally Posted by argentux ...but slack's installer force me to create a GPT partition table.

It's "dos" option in cfdisk.
I have dual boot Slackware/Windows 10 in MBR with lilo as loader. Works ok.

I don't know if this is valid for Windown 10 (used to be for XP, IIRC),
but maybe would be a good idea install first Windows to the first primary partition,
then install Slackware on another partition, then install lilo to the MBR.

are you sure slack-14.2_x64 can be installed on MBR partition table?

Yes - I have done this recently.

My procedure was to use the native Windows tools to shrink the space used by the Windows install to allow for the creation of the Slackware install. I wanted 20GB for the Slackware install plus a larger partition for a separate /home plus a 2xRAM swap to allow for hibernation.

After booting from the Slackware install media and getting to a root login, I used 'cfdisk' to create an extended partition (my layout requires more than the maximum 4 primary partitions allowed) and then the necessary partitions (type 82 for linux and type 83 for swap).

Then I typed 'setup' to start the install. The Slackware installer does not force you to use GPT.

The problem you will have is that if you use GPT you will need to use UEFI with windows which is not necessary with Linux. So an MBR type install with both Slackware and windows 7 should not be a problem.

Originally Posted by argentux I don't know if w7 lacks support for GPT, but it indeed don't let me install over it. Yes! MBR is acceptable for me, but slack's installer force me to create a GPT partition table. I will search for slack-14.2_x64 over MBR on google. EDIT: are you sure slack-14.2_x64 can be installed on MBR partition table?

It can definitely be installed on an MBR, however, if you boot the installer in UEFI mode, it will prompt you to install the system in UEFI mode, which AFAIK, requires GPT.

Check your "BIOS" for a compatibility/legacy mode... it needs to be enabled to ensure Slackware doesn't try and do a UEFI install. Also, one of my computers would provide me two entries for the Slackware installation drive, one being UEFI and the other being "legacy". I needed to ensure I selected legacy so the installer wouldn't prompt me to do a UEFI installation.

Originally Posted by bassmadrigal It can definitely be installed on an MBR, however, if you boot the installer in UEFI mode, it will prompt you to install the system in UEFI mode, which AFAIK, requires GPT. Check your "BIOS" for a compatibility/legacy mode... it needs to be enabled to ensure Slackware doesn't try and do a UEFI install. Also, one of my computers would provide me two entries for the Slackware installation drive, one being UEFI and the other being "legacy". I needed to ensure I selected legacy so the installer wouldn't prompt me to do a UEFI installation.

I think the problem is here. I read a windows prompt about BIOS. Then forced me to use some cfdisk alternative (cgdisk maybe...don't remember) for GPT table. Will try this next days. Thanks everyone for your time.

Originally Posted by argentux I think the problem is here. I read a windows prompt about BIOS. Then forced me to use some cfdisk alternative (cgdisk maybe...don't remember) for GPT table. Will try this next days. Thanks everyone for your time.

fdisk is able to do gpt now too. fwiw

Originally Posted by khronosschoty fdisk is able to do gpt now too. fwiw

Good to know. I always use cfdisk and I prefer it over fdisk due to its simple gui.