lobotomizing Windows for fun, diary of a masochistic Linux slime
So for reasons I am looking into having a second, smaller drive for running Windows 10. However those who know me well can probably infer it will look nothing like a normal windows install (and be right). I like removing as many system components as possible, and replacing them with open source hobbyist replacements that don't rely on Windows update. You can probably guess a few defaults applications I will purge before I even let an installer hit my disk with I/O. I will modify the install with some tools used by IT administrators who customize windows images, find out exactly what is required to run a windows binary using GPU acceleration on my device, and then immediately begin making even more drastic changes before I even touch replacing the default userspace. Something I am looking into is using BTRFs for Windows. Yup. You heard me right. This will require replacing the bootloader with one that can load Windows off of Btrfs, so that once the ntfs to Btrfs in-place conversion is finished Windows can still boot. Here is the bootloader project for anyone else who has serious personal issues: https://github.com/maharmstone/quibble
Then at that point, I can take and manage btrfs snapshots of my Windows 10 install from my Linux drive, and not to mention easily mount files and folders from either OS. In practice I will be chainloading this homebrew bootloader from Grub2 which I already have configured to boot directly into snapshots of my Arch Linux. So while I might not get grub-btrfs automatic snapshots (for Windows) on the Grub2 menu, Linux will always be a rock-solid recovery option, and will be able to rollback irreparable changes I've made by grievously mangling the fundamental default Windows 10 userspace elements via snapshotting. I'm gonna delete explorer.exe with NO FEAR.
#Btrfs #DualBoot #Windows #Linux #Slime #Lobotomy