this post was submitted on 07 Feb 2024
44 points (100.0% liked)

Linux

1257 readers
53 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
 

Edit2: OK Per feedback I am going to have a dedicated external NAS and a separate homeserver. The NAS will probably run TrueNAS. The homeserver will use an immutable os like fedora silverblue. I am doing a dedicated NAS because it can be good at doing one thing - serving files and making backups. Then my homeserver can be good at doing whatever I want it to do without accidentally torching my data.

I haven't found any good information on which distro to use for the NAS I am building. Sure, there are a few out there. But as far as I can tell, none are immutable and that seems to be the new thing for long term durability.

Edit: One requirement is it will run a media server with hardware transcoding. I'm not quite sure if I can containerize jellyfin and still easily hardware transcode without a more expensive processor that supports hyper-v.

top 15 comments
sorted by: hot top controversial new old
[–] kevincox@lemmy.ml 14 points 9 months ago

I use NixOS for this. It works wonderfully.

Immutable means different things to different people, but to me:

  1. Different programs don't conflict with each other.
  2. My entire server config is stored in a versioned Git repo.
  3. I can rollback OS updates trivially and pick which base OS version I want to use.
[–] ShortN0te@lemmy.ml 9 points 9 months ago (2 children)

As of my understanding, immutable systems are useful for Devices that are more bound to change, like a Desktop you actually use to install programs try out things and so on.

I do not see much benefit here for a stable server system. If you are worried about stability and uptime, a testing system does a better job here, IMHO.

[–] uzay@infosec.pub 2 points 9 months ago

Immutable systems are useful for separating the system and application layers and to enable clean and easy rollbacks. On servers the applications are often already separated anyway through the use of container technologies. So having atomic system updates could enable faster and less risky security patching without changing anything about how applications are handled.

[–] Sightline@lemmy.ml 1 points 9 months ago* (last edited 9 months ago) (1 children)
[–] pupbiru@aussie.zone 1 points 9 months ago

my other server is a cloud tho

[–] giloronfoo 7 points 9 months ago (1 children)

Would Truenas fit as immutable? I guess it doesn't stop you from changing things, but doing so might break the next update.

Configuration can be exported. Disaster resolution of fresh install and restore configuration has worked for me. No data loss and even the Virtual Machines started right back up.

[–] xia@links.hackliberty.org 1 points 9 months ago

One could argue that they do "try to stop you"... technically... by disabling the execute bit on software update tools (like apt & deb)... but I see that more as a gentle reminder and acknowledgement of your ownership of the machine, as they could have easy just not had those tools present at all.

[–] BCsven@lemmy.ca 6 points 9 months ago

MicroOS from OpenSUSE. nice thing is initial config at boot is similar to nix config where you can set everything like network, user, passwords, installed packages, etc. this is done via ignition and combuation files. Has a handy file creator to make life . https://opensuse.github.io/fuel-ignition/edit

[–] j0rge@lemmy.ml 5 points 9 months ago* (last edited 9 months ago)

Flatcar linux (this is what I use for my NAS/homeserver) and CoreOS are both good.

edit: OpenSUSE has microOS: https://microos.opensuse.org/

[–] Pantherina@feddit.de 4 points 9 months ago* (last edited 9 months ago) (1 children)

github.com/secureblue/secureblue

It has a server variant!

I find it easier to use than CoreOS as I never dealt with learning how to use this ignite thing. And also they are hardened, which is important especially for servers.

[–] WetBeardHairs@lemmy.ml 3 points 9 months ago (1 children)

Oh I like the look of that.

[–] Pantherina@feddit.de 2 points 9 months ago

It works great, after dealing with lots of the opinionated stuff, adding a userns variant, making Flatpaks work, disabling CUPS instead of removing it etc it is now very usable on the Desktop.

Server should just be as good. Use Podman for containers, installing Docker will weaken the security I guess.

[–] dan@upvote.au 3 points 9 months ago

I'm using Unraid, which is built on top of Slackware. It has a very nice Docker web UI for apps like Jellyfin. It's not immutable though. I don't know of any NAS-specific OSes that are immutable.

[–] lemmyvore@feddit.nl 1 points 9 months ago* (last edited 9 months ago) (1 children)

Typically on a home server you would virtualize services anyway so it really doesn't matter what distro is running on the metal.

And also if you're fully virtualized you can switch out the host distro anytime you want, so you can adopt an immutable one later if you want.

Why do you want an immutable distro anyway?

[–] WetBeardHairs@lemmy.ml 1 points 9 months ago

I want immutability because I come from a the debian world where everything just works. But I want the benefits of using modern versions of packages.