this post was submitted on 15 Nov 2024
19 points (91.3% liked)
Linux
48315 readers
1217 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I can vouch for Linux Mint / LMDE; their pre-installed software and defaults seem very sensible and I need far less set-up, fixing and fiddling (esp. with NVidea hardware; the open-source driver refused to make anything run on GPU with my Asus ROG Strix GTX 970) then on bare-bones Debian or Ubuntu LTS.
All four mentioned here have very stable and safe release schedules.
Bazzite's defaults help a lot with gaming (and that stupid NVidea driver) and the initial welcome-screen helps you install the Steam, Lutris, OBS, etc. you want and leave out anything you don't. It's actually helpful, really!
I do want to add Bazzite's team seems to have only one person who can sign releases, and they did misplace a key at least once leading to nobody receiving updates until they replaced the key in their installation.
Their team management does not seem the best; assuming this was a one-off thing Bazzite can still be a great, stable choice.
Not to be "that guy," but I would like some sources on this. As far as I understand it, the signing happens automatically in GitHub via the private keys during the automated build process.
Additionally, they didn't misplace a key; they didn't yet have a process in place for pushing a new key to end-users (they had/have a plan to rotate their signing keys from time to time). Details about what happened can be found here. In my year of using Bazzite, I haven't seen this issue reoccur, so I am writing under the assumption that they've indeed fixed the internal process that caused the problem.