Thank you for sharing those links, I have been struggling with making rpm-ostree compose
go from a yaml to an ISO, these look like they might reduce the level of effort!
Thank you for sharing those links, I have been struggling with making rpm-ostree compose
go from a yaml to an ISO, these look like they might reduce the level of effort!
It’s atomic! If the latest version you try has issues you can roll back to the last one that was working. It’s really cool. You cannot write to anything other than /etc and /var unless you make a reversible commit on top of the system base image.
Yeah OpenWRT is incredibly slim. I remember doing a double-take looking at their install page because the memory requirements are so low. I’m used to seeing numbers in GB and they’re saying they can provide full functionality in 64 MB.
No onboard eMMC? Are you able to run this from a read-only SD? That’s kinda intriguing, I figure eMMC could be one of the weakest links on an SBC.
Yeah, I think it’s an unusual case, but I wanted to bring it up to support your point about rejecting their kernel and distro. You can put Incus on a lot of different systems. Don’t like systemd? Put it on Void. Want a declarative setup? NixOS. Minimalist? Alpine.
Do I want to maintain a full operating system just to run this one type of software? No, that’s absurd. I want to choose the distro I want to work with and then have the software work on top of it.
I think I was on a previous account the last time I saw you, glad to see you’re still posting. You convinced me to move from Proxmox to Incus a while back. Sure, I had some growing pains, but it’s pretty smooth now.
I like that I can switch out my distros underneath Incus instead of being stuck on one weird kernel. IME you were absolutely right about that. I’m getting into atomic distros to manage homelab machines. I would not be able to do that on Proxmox.
I also don’t need to edit a giant Javascript file to remove a nag about enterprise software repos, which is nice.
You have to follow the attribution and share-alike parts of the license. Otherwise you’ll have the same consequences as an AI company would scraping it (still zero).
I’m not fighting for this shithole country unless I am fighting against MAGAs instead of for MAGAs.
As long as the Sackler family pays him after the ruling it is all legal.
Have you tried “arrete?”
Oh dang that seems like a nightmare. It does seem like it is going through some growing pains particularly with kernel mods.
You can tell it is fake because an omnipotent being required the torture of an unrelated party before it cleared a wholly fictitious debt. That’s some mafia shit.
The problem I’m running into is attempting to create an image fresh from the yaml “treefile” and building on that. I think I know what they’re using but the documentation on how to reproduce the build isn’t great.
I’d also like to isolate the build into containers, which makes the whole thing harder because the build process uses containers and loop devices.
You might get up and running faster if you start from an existing atomic distro and layer packages on top. The ublue-os repos have an automated script that you could use as a reference.
What on Earth.
We have finally invented the Torment Nexus from popular novel Don’t Invent the Torment Nexus.
Me [facts are making me sad]: the word “bad” is literal Nazi genocide, please switch to “plusungood.”
It is indistinguishable from satire. The screenshot comment could be satire and the mod unable to distinguish it.
Hell yeah! I’m on Bazzite, myself. I’m ok with KDE but might swap it out later. Did you rebase to get from Bazzite to Sway?
I think the ostree stuff is really neat. Nix sounds like a great complement to it, I guess you can configure it to install to /var pretty easily? I think I’d prefer that to brew.
I’ve been interested in ostree so much that I’m moving a few other things over to IoT. Building your own makes too much sense, updating layers is so slow. I’m trying to use rpm-ostree compose
to make my own version of IoT but I am struggling to modify the containers it builds or turn them into ISOs. All of their tooling is needlessly complex.
How do you unit test something like that?
Hey, I just some someone else post some resources that you’d probably be interested in:
https://blue-build.org/
https://github.com/ublue-os/image-template