Not a bad idea :)
You're hitting a problem I have with Ublue as well. I wanted to experiment with immutable distros last year, but Ublue provided extremely little information on how their different flavors actually differed under the hood. I ended up having to search through their forums for like an hour to find snippets of how their different when some people asked, but it was never comprehensive.
From what I recall, Bazzite had a few kernel optimizations for gaming, and received updates at a faster frequency than Bluefin, with one of the devs saying that Bazzite would be more likely to experience regressions due to it being more bleeding edge.
Looking at Bazzite's front page now, they actually seem to be doing a better job of mentioning what's unique about it than when I last tried it. But Bluefin and Aurora are still ambiguous.
It's always been based on stable, AFAIK.
Maybe the notebook needed newer kernel code?
If it was able to boot the Live USB to install it, I figure that means the kernel is new enough to actually run the laptop properly. I can only guess something in the installer itself was messing up somehow? Or perhaps it wasn't making an entry in the boot table? That's an odd one for sure.
Only Bluefin LTS is based on CentOS. Standard Bluefin is based on Fedora.
LMDE is not based on Sid, it's based on Debian Stable. LMDE 7 is currently based on Debian 13 Trixie. You sure you had the right ISO?
Cinnamon was written from scratch to reflect a more traditional desktop metaphor. It was not created from existing GNOME code.
Many parts of Cinnamon were forked from Gnome 3 and Gnome 2 (Mate).
- XPlayer was forked from Gnome Videos (Totem)
- Xviewer was forked from Eye of Gnome
- Xreader was forked from Atril from MATE (itself a fork of Envince from Gnome 2)
- Xed is a fork of Pluma (itself a fork of Gedit 2)
- Cinnamon's compositor, Muffin, was forked from Gnome 3's Mutter compositor
Many other parts of Cinnamon are made from scratch, but it is not wrong the say it's also a Gnome 3 fork in many ways.
An unexpected but welcome update, the Fluxer dev agreed to remove the CLA, which puts it back in the running.
EDIT: The Fluxer dev has agreed to remove the CLA!
Just a heads up to anyone interested in Fluxer: there's a huge red flag; it has a contributor CLA that could allow it to change to a non-FLOSS license in the future. I was hopeful for it previously, but that kills it for me.
EDIT: The Fluxer dev has agreed to remove the CLA!
Just a heads up to anyone interested in Fluxer: I was just informed today of a huge red flag for Fluxer; it has a contributor CLA that could allow it to change to a non-FLOSS license in the future. I was hopeful for it previously, but that kills it for me.
Have safe travels, poVoq!
view more: next ›
You're welcome :)