Interesting. Do they point to arch repos or provide their own like Manjaro? I haven't thought about a rolling release atomic distro before.
this post was submitted on 08 Jun 2024
265 points (97.2% liked)
Linux
48178 readers
896 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
Just the Arch repos with an additional repository (similar to EndeavourOS), so AUR packages do work as intended and are in fact officially supported.
(disclaimer: blendOS dev here)
Neat!
Also, the full disclosure of association/potential bias is absolutely appreciated. 🍻
load more comments
(1 replies)
Just wanted to add that OpenSUSE MicroOS uses Tumbleweed repos by default, so I'm fairly sure that's an atomic rolling release too. Not 100% sure, though.
Sweet, been waiting for this one. I wonder how it will compare to NixOS or Kinoite.
*Fedora Atomic
Its a huge bundle of tons of variants, likely 40 or so, if you take everything that uBlue, wayblue and secureblue produce
And that's without counting the roll-your-own variants. uBlue has been a remarkable project.
- Fedora Atomic has been a remarkable project ;D
Fedora builds the container images, even though they themselves use OSTree remotes. There is a Change Proposal to change to them.
This means they continuously build the container images without even using them!
Only because of that the standard container workflow actions (they use an Ubuntu container!) even work. But for sure their tooling is very useful
I just wanted to say this is all very confusing. I barely installed Ubuntu on my laptop as a daily driver mostly due to the MS Recall debacle. It's fine, it's great. However, reading all the Linux Lemmy posts makes me feel like I'll never understand. I know all these words and what they mean, just not in an OS context.
Think about it this way: going onto Linux communities and listening to what people say can be like listening to car mechanics chat.
But do you need to know what all of that stuff means to drive your car? Nah. But that info could come in handy, if you wanted to modify your car or something like that.
You don't need to know what Wayland/X11, PipeWire, GTK4/Qt6, or anything like that is, in much the same way you don't need to know what PowerShell, Event Viewer, NT kernel, or registry are to use Windows.
Welcome to the Linux community. :)
You will probably never understand everything about Linux and all of its included and associated systems. That's completely fine, no one does! That's why we are many, and it's what asking for advice or help is for. You can just learn whatever interests you at your own pace, and know that there will always be interesting things you haven't seen yet.
You probably think of yourself as pretty knowledgeable regarding Windows, but have you ever studied for a Microsoft certification exam? This in depth knowledge is not something the average user needs for his daily usage, but can be interesting to read/know.
Don't sweat it. There were people doing advanced things in Windows that would probably have blown your mind as well. It's just that most people that use Linux just enjoy tinkering for the sake of tinkering so it's more visible, and Linux lends itself to people doing weird and wonderful things never envisioned by it's creators.
You just started on the road, where you stop is entirely up to you. Just know that the view is way more interesting going this route. Take a few pictures on the way.
- repeat the “Don’t sweat it.”
- Ubuntu is a perfectly fine starting point (the other “beginner distro” that’s commonly recommended is LinuxMint)
- »AFTER« you become comfortable with what you have:
- try familiarizing yourself with the command line
- far more competent than Windows
cmd.exeor PowerShell - [email protected]
- far more competent than Windows
- get overwhelmed with all the distro choices available
- get bitten by the distro-hopping bug (“Gotta try them all!”)
- and then try Distrobox (“ALL the distros at once!”)
- get bitten by the distro-hopping bug (“Gotta try them all!”)
- try familiarizing yourself with the command line
- »THEN« take a look at immutable distros
- “immutable distro” is a catch-all term that embraces several concepts
- immutable – the root filesystem is set to read-only – makes it harder to mess up your system
- declarative – your hardware and packages and configs are declared in a master configuration file
- atomic / transactional – updates are checked as they’re applied, if it fails, it gets rolled back to a previous “safe state”
- container / sandbox – ex. Flatpak or Docker or OCI – apps are isolated in their own sandbox and not allowed to mess up anything else
- “immutable distro” is a catch-all term that embraces several concepts
It's fine you don't have to understand any of these just use the computer normally and you're good
load more comments
(7 replies)
How does it compare to NixOS rolling?
I don't think that this one is as reproducible and declarative as NixOS or Guix.
This is just NixOS with extra steps
A very dumb question probably, but I'm new to using Linux so I lack a lot of understanding: I'm on Bazzite atm. Would there be a simple way to switch to blend OS without wiping everything? Like a rebase? Probably not but I figured it's worth a shot to ask xD
No such thing, we all start somewhere! :)
Anyway, you could in fact do that if you were thinking of trying out other Fedora Atomic images such as Silverblue and whatnot (see also the ublue page listing tons of others, including your bazzite!). This uses different tooling, so unfortunately not in this case.
Ooh, not just yet (in essence, it’d be hard to migrate over from the system used in Fedora Atomic to that used by blendOS) :( We’re working on a migration script for users from regular ole’ Arch Linux, though.
(disclaimer: blendOS dev here)
Ah well, not the first time I changed distro xD I'll make some space on my drive and test it
bazzite is fedora based? If so, your filesystem is btrfs and your /home is a subvolume, same as your / (root). you can install a new operating system in a btrfs subvolume (e.g. /blendosroot), then have systemd-boot or grub mount it as root and mount your existing home from it.
sadly, there's no noob-friendly way to achieve this, but if you're adventurous, you have enough search terms to make it happen.
I will jump into that rabbit hole, thanks!
I'm new too but I separated by root and home partitions this last install to try and allow that.
load more comments
(2 replies)
I'm not super clear on what being declarative and atomic means in an OS context. Does it mean there's a file describing what packages are installed, kind of like nix?
I am no expert, please correct me if I’m wrong
From what I understand, it’s like Nix but Arch based. The /system.yaml file contains all of the packages installed on the system.
Also it’s the worst when you download an operating system and you realize that it’s mutable
You’re like “oh no I did not want the mutable one I wanted the immutable one”
I know what all words mean
It's new to me, I think it's saying that your system is built up by you declaring what you want in a file, a single source that everything comes from.
It's atomic because each action the system takes is carefully completed rather than bailing out and requiring you to fix something.
It's immutable meaning you declare how you want things to be set up and then critical changes stem from those declarations and nothing else. You would obviously generate preferences, save data, etc. but the files that make the system / packages work are carefully locked.
It's like the concept of flatpaks + structured system defining + modern common sense OS operations?
I already learnt of blendOS two weeks ago, I think in a discussion of immutable distros.
Really looking forward to play around with it some more and maybe replace my Arch install with this.
Does anybody know if configurations are also declarative?
Basically I want some easy way to spin up something arch linux based with my KDE Plasma settings, pacman hooks, grub configurations etc.
Oh yep, they are declarative, and that's what we've tried to implement with /system.yaml. pacman hooks and grub configs can be defined through /system.yaml (through a combination of the packages and commands arrays), but Plasma config is per-user and so wouldn't be possible to declare unfortunately :( you can declare GNOME config though, fwiw
(disclaimer: blendOS dev here)
load more comments
(3 replies)
Very intriguing. Is there a wiki or support forum in the works, too?
Oh, the main utilities exclusive to blendOS have been documented here: https://blendos.co/reference/ And all the installation/post-install guides: https://blendos.co/install/
For support, we primarily use Discord, although there are plans to set up Discourse eventually: https://discord.gg/fvMpV8ZNxD
(disclosure: blendOS dev here)
Cool. Will definitely be giving blendOS a spin in a VM.
load more comments
(3 replies)
Honestly, having a declarative package manager is pretty important.
Consider the following: We've had the transition from Sys V Init to Systemd recently. But what does it actually mean?
It means, that instead of running a command to start a service, you now flip a switch in a clear, standardized way. The advantage is that you can get a table-like overview over all the services that are currently running. You get an overview, in other words. That is worth a lot because it brings structure and clarity into your system.
Now, with package management it's the same way. Instead of running a command to install a package, we should instead give a list of all the packages that we want to have installed, and the package manager should take care of making sure that they are installed. That would improve clarity, because you get a list of all the packages that are installed. It might also increase efficiency if you're installing many packages, because large parts of the work can be done in parallel. And importantly, you get reproducibility. Imagine you just have a file where it names all the packages that should be installed. You can just take that list and copy it to another machine. Now you've cloned your package installations. I guess things like Docker, with their docker files, are kinda already going in that direction. But it would be nice to have support for it in the mainline operating systems.
Is there a "light" version, without a WM? I run Hyprland on my current Arch setup.
Indeed, you can just write your own custom /system.yaml file with the hyprland package (or no WM/DE for that matter). This guide describes how you can do that: https://blendos.co/install/post-install/intro/ (use the 'custom' track and add 'hyprland' to the package list)
(disclaimer: blendOS dev here)
load more comments
(2 replies)
Set 'blendos-base' in your system.yaml, install additional packages, update and reboot.
view more: next ›