this post was submitted on 24 Mar 2025
119 points (95.4% liked)
Linux
52637 readers
909 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
Doesn't ucore also have to restart to apply updates?
Not super ideal for a server as far as maintenance and uptime to have unexpected, frequent restarts as opposed to in-place updates, unless one's startup is completely automated and drives are on-device keyfile decrypted, but that probably fits some threat models for security.
The desktop versions are great!
This is such a weird take given that 99.9% of people here are just running this on their home servers which aren't dictated by a SLA, so it's not like people need to worry about reboots. Just reboot once a month unless there's some odd CVE you need to hit sooner than later.
So why would somebody run that on their homeserver compared to tried and true staples with tons of documentation? 🍿
You're right, they should be running Windows Server as God intended 😆
It's just Fedora CoreOS with some small quality-of-life packages added to the build.
There's tons of documentation for CoreOS and it's been around for more than a decade.
If you're running a container workload, it can't be beat in my opinion. All the security and configuration issues are handled for you, which is especially ideal for a home user who is generally not a security expert.
That is very fair!!
But on the other hand, 99.9% of users don't read all of the change notes for their packages and don't have notifications for CVEs. In that case, in my opinion just doing updates as they come would be easier and safer.
They won't apply unexpectedly, so you can reboot at a time that suits. Unless there's a specific security risk there's no need to apply them frequently. Total downtime is the length of a restart, which is also nice and easy.
It won't fit every use-case, but if you're looking for a zero-maintenance containerized-workload option, it can't be beat.
Run k3s on top and run your stateless services on a lightweight kubernetes, then you won’t care you have to reboot your hosts to apply updates?