Fedora Atomic Desktops • Hacker News Board

Re: Fedora Atomic Desktops

#51

Post by jwells89 » Fri, Feb 09, 2024, 6:00 PM UTC

kaylynb wrote: post #29

I really like Silverblue and run it on a couple of secondary machines (like in my workshop), but it’s still rough for anything off the beaten path. The largest pain points for me: - Any kernel modules. I know Ublue has images but I wish Red Hat would just have an official solution that doesn’t require hacky RPMs and such. - Kernel cmdline args or any initramfs changes: can’t package in image and need to be applied ma…

The kernel modules problem really highlights why the push to do more in userspace in recent years increasingly makes sense. Hope to see more kernel changes to support this push.

Re: Fedora Atomic Desktops

#52

Post by lillecarl » Fri, Feb 09, 2024, 6:04 PM UTC

bsimpson wrote: post #49

jorvi wrote: post #48

Earlier quoted context omitted.

> It uses the standards set for containerization to make userland configuration reproducible as well. There's a manifest (Containerfile) that enumerates all the modifications, which means an upgrade is bump the version of the base image and replay all the modifications from the manifest. Is the containerfile syntax and reproducibility as good as configuration.nix / NixOS? I love NixOS but it’s a very acquired taste,…

I've only used NixOS, but the Containerfile looks more like a shell script than a Nix config: https://github.com/ublue-os/bazzite/blob/main/Containerfile

That looks like something I wouldn't wanna use, all imperative

Re: Fedora Atomic Desktops

#53

Post by thesuperbigfrog » Fri, Feb 09, 2024, 6:04 PM UTC

colordrops wrote: post #39

WTF is a "spin"

A Fedora distro with a different desktop (or sometimes a specialized purpose):

https://fedoraproject.org/spins/

Re: Fedora Atomic Desktops

#54

Post by lproven » Fri, Feb 09, 2024, 6:08 PM UTC

smm11 wrote: post #40

Don't use immutable distros on machines you might need for bootable disc or bootable thumb-drive use in the future. Found that out the hard way.

> need for bootable disc or bootable thumb-drive use

What does this mean?

Re: Fedora Atomic Desktops

#55

Post by Andrex » Fri, Feb 09, 2024, 6:09 PM UTC

bsimpson wrote: post #21

I know that Silverblue and Kinoite are more established, but I would have liked to see a consistent rebrand. "Fedora GNOME Atomic" is a better name for the same reasons that "Fedora Sway Atomic" is.

It would be called "Fedora Workstation Atomic" unless they wanted to rename the Workstation branding too.

Keeping Silverblue makes sense to me with that in mind. I feel like Fedora Kinoite should be renamed though. The one "halo" distro can use a distinct name but everything else should follow the new pattern IMO.

Re: Fedora Atomic Desktops

#56

Post by NewJazz » Fri, Feb 09, 2024, 6:17 PM UTC

bsimpson wrote: post #49

jorvi wrote: post #48

Earlier quoted context omitted.

> It uses the standards set for containerization to make userland configuration reproducible as well. There's a manifest (Containerfile) that enumerates all the modifications, which means an upgrade is bump the version of the base image and replay all the modifications from the manifest. Is the containerfile syntax and reproducibility as good as configuration.nix / NixOS? I love NixOS but it’s a very acquired taste,…

I've only used NixOS, but the Containerfile looks more like a shell script than a Nix config: https://github.com/ublue-os/bazzite/blob/main/Containerfile

Containerfile is just what the IBM containers group calls a Dockerfile. They are 99% compatible.

Re: Fedora Atomic Desktops

#57

Post by dabber21 » Fri, Feb 09, 2024, 6:22 PM UTC

I'm using Silverblue for 2 years now it is very nice to consume things, but it gets tedious when you want to some development, so I really just use it to play Steam games (flatpak), watch videos and browse the internet.

never had any issues so far for those use cases

its definitely something I'd install for my parents

Re: Fedora Atomic Desktops

#58

Post by jorvi » Fri, Feb 09, 2024, 6:26 PM UTC

LelouBil wrote: post #50

jorvi wrote: post #48

Earlier quoted context omitted.

> It uses the standards set for containerization to make userland configuration reproducible as well. There's a manifest (Containerfile) that enumerates all the modifications, which means an upgrade is bump the version of the base image and replay all the modifications from the manifest. Is the containerfile syntax and reproducibility as good as configuration.nix / NixOS? I love NixOS but it’s a very acquired taste,…

It's not as exactly reproducible because there's no version locking, however after running the Containerfile you have a snapshot of the filesystem that is ready to be used and that you can save. Universal blue images use GitHub container registry, and it's 90 days of history to have at least 90 days of rollbacks available. I'm currently setting up a Bazzite machine by using a GitHub actions to build every day an imag…

Thank you for the info!

Re: Fedora Atomic Desktops

#59

Post by LooseMarmoset » Fri, Feb 09, 2024, 6:28 PM UTC

bsimpson wrote: post #28

If you're not familiar, the Atomic project is really interesting. Its focus is stability and reproducibility, trying to solve the fragility that can happen when the default way to use software in Linux is `sudo apt-get install`. There's a community offshoot called Universal Blue (after the original Atomic image Silverblue). It uses the standards set for containerization to make userland configuration reproducible as…

Can you explain what you mean by:

"the fragility that can happen when the default way to use software in Linux is `sudo apt-get install`"

Re: Fedora Atomic Desktops

#60

Post by FireInsight » Fri, Feb 09, 2024, 6:29 PM UTC

Daegalus wrote: post #43

bsimpson wrote: post #28

If you're not familiar, the Atomic project is really interesting. Its focus is stability and reproducibility, trying to solve the fragility that can happen when the default way to use software in Linux is `sudo apt-get install`. There's a community offshoot called Universal Blue (after the original Atomic image Silverblue). It uses the standards set for containerization to make userland configuration reproducible as…

I will say, I prefer Bazzite for dev too. In general Project Bluefin is newer, but seems to be trying to get into gaming too. Likewise, Bazzite is considering developer images also. So I might switch to those. But it's so easy to switch. I currently use Bazzite + Nix + HomeManager + Flatpaks and it has been fantastic. I only layer Tailscale and a few minor things that need be system level to operate right.

Bluefin is actually older, it's the base that kickstarted the whole development of Universal Blue. They are pretty much as mature, too. Bazzite is more gaming oriented, Bluefin more general purpose. Bazzite is way more popular since gaming attracts people.