this post was submitted on 15 Nov 2024
20 points (91.7% liked)

Linux

48726 readers
880 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
20
LF Distro (lemdro.id)
submitted 1 month ago* (last edited 1 month ago) by MrTHXcertified@lemdro.id to c/linux@lemmy.ml
 

I need recommendations for a stable release distro for OBS Studio livestreaming and light video editing. This machine will be shared between several users who are techies, although not necessarily Linux (they're coming from Windows). I don't want to worry about things breaking because of an update, or to start a shoot only to find problems once we're live.

Nvidia and nonfree codecs should be treated as first-class citizens. H.264 w/ AAC will be everywhere with this workflow.

Some thoughts:

Linux Mint Debian Edition: Currently my top choice. It just works?

Fedora Bazzite: My second choice, maybe with auto-update disabled. Seems a bit risky though in the case of security updates to packages.

OpenSUSE: I run Slowroll on my laptop and work desktop, however recent package management errors relating to codecs and the packman repo have spooked me away.

Debian: Release cadance seems too slow for my preference.

you are viewing a single comment's thread
view the rest of the comments
[–] Telorand@reddthat.com 2 points 1 month ago

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.

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.