Avatar

j0rge

j0rge@lemmy.ml
Joined
0 posts • 44 comments
Direct message

She only suggested a small “news channel” built into the OS.

Yeah we’re working on that here: https://github.com/ublue-os/bluefin/issues/1485

The failure with secure boot afterwards is news to me, we’ll investigate, thanks!

permalink
report
parent
reply

Did you experience the Silverblue issue on a ublue image? We mitigated that last month so you should only have one problem or the other, not both.

permalink
report
reply

there are a lot of tools included that are new to me, despite being a cloud-oriented developer.

Interesting! What tools do you commonly use?

permalink
report
parent
reply

We probably won’t (we’re not looking to grow that much anymore), but I think someone should definitely take either portainer or the proxmox stack and just slap it on top a CoreOS image with a user friendly installer and make a killer SMB server.

permalink
report
parent
reply

Here’s the repo: https://github.com/ublue-os/bluefin and the intro doc outlines some of the features. We include all the codecs from rpmfusion and use negativo17 for the nvidia drivers.

permalink
report
parent
reply

Yeah checkout ucore, which is derived from CoreOS instead of Silverblue: https://github.com/ublue-os/ucore

permalink
report
parent
reply

What kind of printer? What’s the name of the package that got it working? We can add printer drivers pretty easily.

permalink
report
parent
reply

Hi! Universal Blue co-maintainer here, here’s the TLDR. You’ve got the basic descriptions right, “Universal Blue” is mostly the parent organization that holds everything in github.

We take Fedora’s Atomic OCI images and customize them for different use cases (Aurora, Bazzite, and Bluefin) and then publish base images so people can make their own versions of whatever they want. So if you wanted to take Silverblue, Kinoite, and make your own custom image you can mostly just grab whatever you want and shove it into an OS image. Bluefin started off as a “fix me” script for Silverblue that added all the stuff I wanted and then once I was shown what Fedora wanted to do with it the natural progression was to just make it a custom image. We just released 3.0 a few minutes ago actually!

Basically in Fedora 41 the tech will become more widely available with official OCI base images and better tooling. We just decided to start way earlier in the process so we could get all the automation out of the way, build a community, get familiar with it, etc. Happy to answer any other questions you may have!

permalink
report
reply

Flameshot is 3.6MB on disk according to flatpak info org.flameshot.Flameshot

permalink
report
parent
reply

ublue co-maintainer here. I go over a bunch of the reasons here: https://www.ypsidanger.com/homebrew-is-great-on-linux/

Namely we needed a way to complement Flatpak and brew was a natural fit. It’s an ecosystem reason not a technical one. It has everything we need and a good deal of Bluefin’s target audience are already using it on mac. So for us it’s an easier lift to just add homebrew and move on to larger problems.

Plus it’s nice that they’re working with the openssf to secure the supply chain pipeline, and it’s nice that everything is in github where we can inspect it, use the same tooling we use for the OS, etc.

permalink
report
reply