


That is a very good suggestion, I'll definitely consider that. I was thinking about possibly testing in virtual machines and just leaving my Gentoo Experimental drive for testing updates on my hardware before pushing to my Stable drive - though that might seem overly cautious, I am a Gentoo noob and very OCD about packages and drive organisation and clean up.The Doctor wrote:A much more elegant solution to that problem is to use a kvm or virtualbox solution to do the testing in a virtual environment. This includes the ability to use snapshots etc. This not only reduces wear but allows you to keep multiple testing platforms in place. Personally, I would ditch the 3rd SSD and replace it with another 1 TB drive to hold the data for multiple virtual machines.
I do plan to use Windows 7 if possible, I don't trust Windows 8 to be developed and tested enough to be safe and stable yet. Consider it took XP and Vista several years of being on the market to be anything like a viable OS, Windows 8 is just too new. I'll look into the different partition methods, I still am not sure where I'm going to load GRUB 2 though. I've heard it's always preferable to load it on the Linux MBR as Windows apparently overwrites the MBR with it's own crap if intalled under the Windows partition. Is that still correct?The Doctor wrote:And if this is a new computer you would almost certainly be better served by using GPT partitions and the built in EFI boot manager or rEFInd according to taste. This is particularly true if you are going to use Windows 8. One advantage of using the EFI boot loader is that the boot process for the default choice won't be slowed down for a boot menu unless you enter the boot menu in a similar way to entering the BIOS configuration screen.

It might be, but I think windows checks what disk is being booted from and installs there. I had a computer where sdb was the drive where windows was installed (by the factory) but the mbr used was on sda along with my gentoo instillation. The only time I have ever seen Windows do anything like rewritting the MBR is after a major update, as in Windows 8 to 8.1. I wouldn't say it should be a major concern.I've heard it's always preferable to load it on the Linux MBR as Windows apparently overwrites the MBR with it's own crap if intalled under the Windows partition. Is that still correct?

Thanks so much for your insight. Yes I definitely want to split up Windows and Linux, they don't play nice together so to avoid the trouble (and as I have the cash) I don't mind investing in a few SSDs just to save myself the trouble. So I guess something like this..creaker wrote:I have 3 Linux installation + 2 Windows installation + LinuxMint Live DVD iso. All these systems located on two drives and Grub2 manages all these systems.
/dev/sda1 - Gentoo Linux (Grub installation and /boot directory are here)
/dev/sda2 - Gentoo Linux (No Grub installation)
/dev/sda3 - Windows 7
/dev/sda5 - File Storage Partition
/dev/sdb1 - Windows XP
/dev/sdb6 - Gentoo Linux (No Grub installation)
/dev/sdb7 - File Storage Partition.
Grub binaries are installet at /dev/sda mbr.
If you planning to install your Linux with /boot at the same drive with Winsows, Windows should be installed in the first place because it will rewrite mbr.
If you planning to dedicate a whole SSD for Windows (or Windows + File Storage) this case no matter when you will install Windows. You have just to set SSD wint bootable Linux as a primary boot device. I think it is better option (to separate Windows (e.g. at /dev/sdb) from Linuxes (e.g. at /dev/sda)), if you will get some trouble with Grub bootloader (/dev/sda) you will be able to use Windows still (using Windows bootloader at /dev/sdb mbr)


Thanks for the link, I'll give it a read.srs5694 wrote:In my experience, GRUB 2 often falls down on more complex setups, with "more complex" being somewhat subjective, but ranging from two to four OSes and up. Basically, when using GRUB 2, you're forced to do one of two things:
IMHO, GRUB 2 is the worst boot loader available for EFI-based systems. See my Web page on EFI boot loaders for my thoughts on them all. (Note that I'm not unbiased -- I maintain rEFInd, which I intend to work with minimal configuration effort.)
- Rely on GRUB 2's auto-detection, which usually works well for whatever distribution you're using, works OK for Windows, and is a crap shoot for anything else. If something breaks, fixing it is like walking on broken glass.
- Disable GRUB 2's auto-detection and configure everything manually. This is possible, but it starts to become painful with a lot of distributions because you'll be constantly editing grub.cfg with kernel updates.
Windows 7 works fine with EFI, although as ct85711 noted, you may need to jump through some hoops to get its installation medium to boot in EFI mode.
I really want to try to keep things as simple as possible.ct85711 wrote:Another thing to note, is that while you could do a hybrid setup (mixing mbr with efi boot); it is not supported too well on any system, and you'll more then likely have a larger headache than necessary try to do that. So I recommend sticking to only UEFI or MBR boot for everything and not mix between.