| ▲ | fhd2 4 hours ago | |||||||||||||
I typically install both systems on the same disk, different partitions. Then work with additional SSDs strictly for game storage. Only annoying bit is that some games _need_ to be on C, but very few in my experience. If you have enough space to shrink your Windows partition, that could work without waiting for an SSD. Though I guess the one OS per disk setup is ultimately cleaner. Been dual booting for >20 years now. It's nice that some games work on Linux pretty well these days, and of course I had fun messing with Wine manually to get some stuff to work decades ago. But it really doesn't bother me too much to reboot when switching between gaming and literally anything else. | ||||||||||||||
| ▲ | keyringlight 3 hours ago | parent [-] | |||||||||||||
The issue that has occurred a few times is that some windows updates will decide that they 'own' the disk it's installed on or knows better than whoever is running the system, and overwrite any other boot manager with window's own and you may need to break out a live boot to recover it. Using a single isolated disc at OS install time (if you can have multiple physical drives) and using a motherboard boot selection hotkey means that risk likely goes away. | ||||||||||||||
| ||||||||||||||