Is switching a good idea?
Is switching a good idea?
Recently I've been considering switching to a Linux-based operating system. I explored SteamOS because of its focus on gaming and its compatibility with AMD hardware. However, I'm weighing the options among various choices like HoloISO, Steamo, and Bazzite, trying to figure out which fits my requirements best. As a note, I'll still keep my old Windows as a backup in case anything goes wrong.
I’m going to try something different and see what happens. Experiment a bit and discover what works best for you. Check where it performs well and where it struggles. If you’re unsure, look through other articles or lists for any OS you missed initially. In the coming months, I expect SteamOS could become a strong contender, but it’ll probably need some major improvements in the first half to handle edge cases effectively.
You're curious about the concept of running two operating systems on a single computer. That's an interesting setup! It can offer flexibility and performance benefits depending on your needs. Would you like to know more about how it works or what advantages it provides?
I completely agree with OddOod, you should discover which distribution suits you best. Most options include a live USB to test before committing and seeing how the interface feels. If you’re still unsure, dual boot it for a safety net and reduce frustration during setup. When possible, take advantage of free ports like SATA or NVMe and have some extra cash on hand—it’s simpler to reuse drives later than constantly shifting partitions. If not, you can always create a second partition, but be careful not to accidentally delete your Windows files during installation. I still think it’s wise to experiment a bit if something doesn’t work right away; sometimes it’s just a minor issue. My partner and I no longer use Windows for gaming; we switched about a year ago after dual booting on our rigs, and we don’t plan to go back. Ultimately, it depends on the games you play. Most modern titles support Steam Proton or Lutris/Windows, so check ProtonDB with your favorite games for a quick check. Anything needing online anti-cheat might run into trouble, as those systems often block access and could lead to bans.
Switching often proves beneficial since Microsoft has introduced practices that make Windows difficult to use, adding unwanted software and raising privacy issues. It’s also important to note that a "gaming distro" doesn’t magically boost performance or guarantee smooth operation on all systems. You might find some packages work better on one platform than another, but overall distributions tend to be quite similar. Most come from a small set of core developers, sharing drivers and packages with minor variations. The rest usually just offers tailored experiences for specific needs, improved installation ease, or focused QA for particular tasks like gaming. SteamOS stands out as an exception, though it still isn’t a strong alternative for general use. After years of using Linux, I’ve seen different preferences and trade-offs, but I’ve never experienced a major shift in daily performance. I’m generally neutral toward Ubuntu and its versions—it’s a poor choice for most users and should be avoided. If you’re considering a change, explore options carefully. Think about how crucial it is to have the latest software updates and whether you value stability over cutting-edge features. If you prioritize reliability and a predictable update schedule, Debian or Fedora could suit you better. For those eager to dive deep into Linux, Gentoo is an excellent pick. Flatpak also enhances third-party app support, making it easier to install apps from repositories if they’re not available natively. Ultimately, the best choice depends on your goals—whether you want ease of use, performance, or a strong community backing.
I highly suggest using separate drives. Follow this sequence: connect only the two drives and erase them (SATA/nVME secure erase works quickly via BIOS). Set up Linux on one drive with a sufficiently large EFI System Partition and reserve it completely. Keep the other drive untouched. Install Windows next; it should recognize the EFI System Partition and install its boot loader there. Then create additional partitions on the second drive. This order matters because Windows usually creates a 100MB EFI partition lacking enough space for typical Linux configurations with two kernels (one active, another as backup). It also prevents Windows from occupying space needed by Linux for hibernation—though not strictly necessary in a dual-drive system, I advise turning off hibernation and fast startup to keep partitions clean. The Linux side marks these areas dirty, making them inaccessible to Windows. For the third drive, both operating systems can access it for your Steam library; refer to Valve’s guide here: https://github.com/ValveSoftware/Proton/...nd-Windows.
Regarding distribution, consider moving to Arch Linux and installing it manually using their wiki instructions. It’s a thorough process but offers deep learning. Alternatively, you can stick with Arch for simplicity or explore other distros as needed.
I support the two-drive approach, though I’m not sure it’s ideal unless you anticipate needing to adjust partitions—which can become complicated. Generally, dual-booting on the same drive hasn’t caused issues for me lately. The main concern with single-drive dual boot is the risk of Windows adding a recovery partition that alters the order without damaging data—just a hassle to fix. I’m not sure your concern is about having ESPs on one drive only; if so, it’s not recommended. Having ESPs on separate drives for Linux and Windows is usually safer, as it prevents a failure in one from making the other unbootable. You’re free to have multiple ESPs across the system, though each drive can only host one. The EFI firmware can manage booting, or you can use a traditional /boot partition for your kernels. I usually opt for the latter for stronger file system integrity—ESP should be FAT16 or FAT32. The chance of corruption is low, but FAT is outdated and could be affected by power loss during writes. With a separate /boot partition, the ESP size isn’t critical; around 512MB works fine, though a larger partition (~1GB) might help with backup kernels. Windows ignores unrecognized partitions for hibernation or other tasks, so no major issues there. This is especially helpful if you keep non-OS data on a distinct drive or partition.