#particleos — Public Fediverse posts

The video recording of my #ParticleOS talk yesterday at #fosdem2026 is already online, amazing as always how efficient the video team is! https://fosdem.org/2026/schedule/event/DVVAV9-particle-os-from-trad-distro-to-immutable-image/

Has anyone managed to boot particleOS on virt-manager at all? This seems legit impossible to boot on a vm outside of `mkosi vm` for me...

Basically clone the repo, generate a disk image with `mkosi -B -f`, then try to boot the main `.raw` disk image with `systemd-vmspawn --cpus=4 --ram=1073741824 --kvm=true --tpm=true -i ParticleOS_blah.raw`

It just keeps failing for me with this issue: https://github.com/systemd/systemd/issues/39955

#systemd #particleOS

Why I now have an EMERGENCY file in my /home: https://s1m.fr/systemd-homed-full/

#systemd #ParticleOS

I presented on two topics:

- Together with @zbyszek on the state of the #systemd project, a talk that we try to do every year: https://www.youtube.com/watch?v=JVP-ODCZSUk

- Together with @daandemeyer on dogfooding #systemd and #ParticleOS https://www.youtube.com/watch?v=XgcnKxlIVcc

I also participated in a panel together with other fellow #systemd maintainers where we took questions from the audience: https://www.youtube.com/watch?v=EH3OodT0qJA

#ASG #asg2025

@valpackett

#KDELinux is actually doing what you ask for: 1 ESP plus 1 partition to hold the installed system.
Although they use BTRFS instead of LVM.

#ParticleOS #systemd

@anderslund
Could you tell me what went wrong while using the `dd` way?
I want to try this also on my machine, because at moment I'm trying to setup a fresh system again.

#ParticleOS #kdelinux #kde #plasma #linux

@pid_eins
@bluca

Because it COMPLETELY WRECKED and reformatted both NVME's. 🤯
Even though I instructed to use only `/dev/nvme0n1`
And now I'm left with a PC without any working OS on it, because it didn't work anyhow...

Wish me strength to find energy to setup a new system *again* 🥵
#ParticleOS

@pid_eins
@bluca

Today I finally tried again, but whished I had not...

I KNOW it's my own FUCKING FAULT but argggg...

I have 2 NVME's in my system:
- NVME0 → Dedicated to test setups.
- NVME1 → My main working system.

Both with their own ESP's.
So far so good, all was working fine and I could boot each separately using the UEFI boot menu.

Until ofcourse i was DUMB enough to try #ParticleOS WITHOUT removing my NVME1, containing my main system, from my hardware before doing this test. 🤬

@bluca @pid_eins Nope still not working...
#ParticleOS

So, I've got an interesting problem. I'm trying to install #particleos , but when booting the installed system, there's a boot error message so it boots in emergency mode. I cannot scrollback to the error as this has been removed in recent kernel. And I can't get a root shell because the system root account is not setup. So I can't just know why this is failing. Any idea? @bluca #linux, #systemd ?

@bluca @pid_eins

#ParticleOS - ParticleOS_9.1_x86-64.raw.zst
- https://download.opensuse.org/repositories/system:/systemd/Debian_13_images/

After dd'ing the uncompressed raw image to USB, i rebooted into the UEFI then set SecureBoot to setup mode and booted from the USB.
But seems something is going wrong, because it errors at the root device it seems...

What i'm looking for as a fresh starter is something like this workflow:
1. Download a bootable image, Net-Install or Fixed-Distro-Variant, and put it on a USB.
2. Boot from the image and get prompted, via text or GUI, for disk to partition and install the #ParticleOS.
3. Ability to customize this install by building a new image from within this install which will be used to "update" the booted image.
This step includes adding new packages and a signing key for UEFI-SecureBoot

@bluca @pid_eins Excuse my noobiness but...

I still have no clue which raw image to try.
I tried downloading each `*_images/netesp_x86-64.raw.img` together with it's `.sha256` file, but the checksums don't match even after trying multiple times using `wget`.
```
$ shasum -c netesp_x86-64.raw.img.sha256
netesp_x86-64.raw.img: FAILED
shasum: WARNING: 1 computed checksum did NOT match
```

So i'm still unable to kickstart a fresh #ParticleOS installation to get started with this all 🤷‍♀️

@bluca @pid_eins Thank you for working on that 👍

Are any of those images usable as-is from an USB at moment to get started with #ParticleOS?
If so could you write some documentation about the process wrt. which file to burn to USB to get what result in the README at https://github.com/systemd/particleos

I'm eager to test drive this 😉

@pid_eins Looking forward for such a UKI to kickstart a base #ParticleOS installer from which we can start an installation of a choosen distro...

I'm currently still unable to test ParticleOS due to the requirement of an initial local build.
This step could be done after the above on the installed system if done well IMHO...

The only thing we would need is an UEFI menu entry pointing to the Online UKI that kickstarts this all...

#ParticleOS (finally, #systemd/linux) is a really cool idea in many ways but I absolutely can't stand fixed-size, fixed-number (2, a/b) hard partitioning for the OS images. What is this, Android? idk how to explain it without sounding like the TempleOS guy or something but fixed allocation of storage is literally like, spiritually offensive to me.

Why not at least leverage LVM to have flexible partitions, so that installing a new image would create a logical volume to write the erofs to? And have systemd-homed use logical volumes for homedirs too instead of files on a root fs? At least only one inflexibility would be left (homedir sizes, and even there: ext is shrinkable as scary as that operation sounds). If we're going the partition-ish route, I would prefer the root to not be an FS at all, but a flat thing like LVM that can flexibly contain system images and home dirs.

On the other hand why not only have the one single rootfs and drop the erofs images into it? and then homedirs could be either luks images (and the root is "flat" with only images inside), or fscrypt dirs (if you like me vastly prefer the flexibility to "omg gotta hide the shape of the fs tree too").

Of course AerynOS/moss is the genius solution that provides atomicity without images :p but I do appreciate the "do interesting stuff based on existing distros" thing. AerynOS doesn't have non-amd64 arches so far, and quickly putting together an image based system out of an existing aarch64 distro would've been great for me right now..

Soooooo... has anyone tried building #particleOS fedora with #asahi remix? Most issues will probably be around booting the whole thing with UKIs, as well as the custom installer, I guess?

@daandemeyer

📺 🕹️ Don't miss @ozoned's live stream on Owncast! 🕹️
Watch here: https://stream.ozoned.net/

#LinuxGaming #ParticleOS #LiveStream #RetroGaming #owncast #livestream #selfhosted

#ParticleOS - ein systemd-Betriebssystem.

systemd-Gegner haben es schon immer prophezeit: systemd will ein allumfassendes Betriebssystem werden. Nun erfüllt sich die Prophezeiung.

Naja, ganz so schlimm ist es (aus deren Sicht) dann doch nicht. ParticleOS ist laut Selbstbeschreibung auf GitHub eine vollständig anpassbare, unveränderbare Distribution, die die von Lennart Poettering im Blogbeitrag Fitting Everything Together beschriebenen Konzepte umsetzt.

https://linuxnews.de/particleos-ein-systemd-betriebssystem/