@vwbusguy Thanks for all of your help! Just a few more questions:
1. I should probably call my template something else (because of trademark issues) right?
2. Should this new repo be public?
3. Should I include all branches?
@vwbusguy Thanks for all of your help! Just a few more questions:
1. I should probably call my template something else (because of trademark issues) right?
2. Should this new repo be public?
3. Should I include all branches?
@vwbusguy @UniversalBlue Really!? I've got to try that out with a VM first, but I still have got to try it out!
@vwbusguy Okay, that's great to know. I don't think I'd be able to use Universal Blue without it!
As for Bluefin, the main issue I have with it is the lack of dual-boot support. My main laptop and tablet have only one SSD slot (my laptop technically has two, but the second cannot be used with dual-sided and/or 8 TB SSDs in the main slot), and that is a huge dealbreaker for my use cases. What is the ETA for a fix for dual-boot on a single SSD (with a different Linux distro, not Windows)?
@vwbusguy @UniversalBlue You mean fork the OS image? That sounds cool! Where would I learn how to do this?
(I'd love to be able to make a reproducible image to install on multiple gaming handhelds, for example, if a Steam Deck 2 comes out.)
@vwbusguy For example, I HAD to use rpm-ostree on Bazzite to install the Klassy window decorations (I prefer it to the stock KDE Breeze window decorations in several ways).
Also, I like to be on the almost bleeding edge of software so I can report bugs before more people encounter them and thus help FOSS be better. Unfortunately, afaik, image-based distros make it much less practical apart from using flathub-beta, and that won't work for system packages, like the DE, unless I was to compile it.
@vwbusguy That is true that "immutable" distros are harder to break. However, they aren't "immutable" in the sense of "not being able to be changed. Many of those DO have options to change the OS image underneath, such as rpm-ostree on Fedora Immutable based distros.
What also is true is that to get deeper into the system, it does take considerably more work. (1)
@vwbusguy I think it depends on the use case.
For something like the Steam Deck, immutable distros make perfect sense. Heck, even for newer users to Linux, it can make sense with @UniversalBlue Bazzite, Bluefin, and Aurora. That's thanks to Flatpaks.
That being said, for advanced users like myself, I don't think image-based / immutable distros will take off that much because they're too restrictive.
They're really nice, but they're not a catch-all solution.
The fact that gaming on Linux went from "ha ha, very funny" to most games just work and only a few FPS games are not working at all (and most of them doing so on purpose by blocking Proton in anti-cheat rootkits rather than because of just not offically supporting Linux) is a real testement to both Linux rising as a legitimate computing plaform and Valve's work on making Linux a true gaming platform.
Also, thanks to Jason @killyourfm for this nice article BTW! https://www.forbes.com/sites/jasonevangelho/2024/08/21/linux-scores-a-surprising-gaming-victory-against-windows-11/