Unexpected item in debugging area.

Upgraded all of my working arm64 #postmarketOS devices to the latest #phosh #systemd edge! Also wrote a small script to do all my preferred app installs and some configurations (my custom squeekboard layout, autostart TouchpadEmulator, set default scaling to 200%) to make reinstalling less painful.

How to stop service from starting after boot? #2204 #systemd #apparmor #container

https://askubuntu.com/q/1549890/612

Grafito is a sleek, systemd journal viewer that makes reading system logs easy, with live streaming, powerful filters, and a clean web-based UI.
https://linuxiac.com/grafito-systemd-journal-log-viewer-with-a-beautiful-web-ui/

Ubunutu User Manager fails to start after upgrade to 24.04 #2204 #systemd

https://askubuntu.com/q/1549813/612

Improving EC2 boot time from 4s to 2.8s https://lobste.rs/s/plh9e0 #linux #performance #systemd
https://depot.dev/blog/accelerating-builds-improve-ec2-boot-time

#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..

Continuing my fun with systemd service files - is there any way to pass the definition of the exit codes through?

e.g. my unit.service does an `exit 5` in certain cases.

In journalctl that shows up as 'status=5/NOTINSTALLED'

I think that comes from here

https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#Process%20Exit%20Codes

I'd like it say 5/NOSYNCREQUIRED or similar. I'd be happy to chose codes that aren't pre-defined if that helps?

Is this possible?

As we gear up for the official commencement of our June 2025 Outreachy cohort, we couldn’t do it without our champions of inclusion.

Outreachy extends a heartfelt THANK YOU to the generous sponsors powering this cohort at the following levels:

Ceiling Smasher: @wikimediafoundation.
Thank you for breaking barriers and providing opportunities for underrepresented talents in tech.

Promoter: #RedHat (for @fedora
projects), and @tarides
(for @ocaml projects).
We appreciate you for creating meaningful change and advancement in the free and open source software ecosystem.

Includer: #TheCityUniversityofNewYork [Research Foundation](for @bioconductor projects).
Thank you for championing diversity through targeted support for impactful projects.

Welcomer
@gnome , @nixos_org , @igalia , and @OpenSourceCollective (for @servo ), #Microsoft (#systemd projects), @mozilla, and #Meta.
Your commitment empowers us to support diverse, global talent in open source by providing paid, remote internships to those who face underrepresentation, systemic biases, or discrimination in the technology industry of their different countries.

We're grateful for your continued partnership in building a more inclusive, equitable, and impactful tech ecosystem. Let’s keep smashing ceilings together!

A #reboot is a solution to many tech problems. But if you are on #Linux, did you know you need to reboot only if your kernel has changed? Otherwise you can do a "soft reboot" and get the same thing. You need to kill the init process and make it respawn. It varies from distro to distro but on #systemd ones, you can do systemctl soft-reboot and it'll do the job for you.

Also if you have problem with your graphical shell, you can simply restart your graphical stuff. Not even a soft reboot is needed. For instance if your display manager is lightdm like me, simply do systemctl restart lightdm.

I think this applies to other #unixlike operating systems with the similar kernel and system architecture as Linux. Maybe #BSD people can share their experience?

Не знал что так можно:

sudo systemctl start systemd-journal-gatewayd.{socket,service}

curl -s http://127.0.0.1:19531/entries

curl -s "http://127.0.0.1:19531/entries?UNIT=sshd.service"

curl -s -H "Accept: application/json" "http://127.0.0.1:19531/entries?UNIT=sshd.service"

А ещё там есть вебморда по пути /browse.

#systemd #http #web #logs #journald

UPD: работает шустрее чем Filebeat, FluentBit, FluentD и syslog-ng и не грузит систему излишне, вопрос только чем пушить, но это вопрос решаемый.

Was habe ich schon mit #systemd rum gekämpft damit nen nfs mount nen gewisses network interface abwartet bevor er versucht zu mounten (zugegeben nicht ganz triviales setup mit vxlan auf nem vlan das in ner bridge steckt - aber alles mit systemd-networkd)

Unter #openbsd gibts ifstated, ein daemon der für einen Dinge tut wenn sich am state eines netzwerk interfaces tut.

Nennt mich alt, aber ich halte diese Unix Idee von Ein Ding für einen Zweck nach wie vor für zeitgemäß

https://man.openbsd.org/ifstated

I'm finding the weird politics inside the #Linux world kinda exhausting right now.

Like, guys, I'm a glorified shell script kiddie that cosplayed as a sysadmin for five years a lot of years ago (and hated it).

I don't have the technical knowhow to really dive into just what the flip #SystemD is and why so much money is being poured into it by literally one of the most evil corporations in die flipperwaltd gersput.

I strongly desire to find a good distro to recommend to newbs (including a cow-orker that I will be forcibly upgrading away from Windows 10 later this year), but then I'm divided between the knowledge that I'm adding to the SystemD/Linux userbase (for whatever monstrosity that will some day become), and the fact that non-systemD distros generally can require more effort to maintain, and lack the polish of something like the Fedora-derivatives.

I read this #Debian announcement/note today and kinda flipped my lid:

• Drop systemd-resolved package. The ctte has declared that the way the systemd-resolved tool works is incompatible with their decision to prioritize avahi in Debian. Furthermore, the resolved tool is being used to inflict pain on the maintainer, and induce burnout. Regrettably, the only safe solution to ensure this package is compliant with this decision is to drop it, as all reasonable alternatives put forward have been rejected:
  https://salsa.debian.org/systemd-team/systemd/-/merge_requests/289 (Closes: #1098914)
  (Emphasis added)

WHAT THE FARGLESNUFF DOES THAT MEAN?!?

Can anyone explain to me rationally what in the world is happening in the Linux world?

Because the obviously anti-systemd crowd are still mostly talking about PID 1, which I'm honestly not that concerned about, and the pro-systemd crowd are all like, "No, no, it's great you're all being crazy, I got the Harkonnen blood plug just last week and it feels great!"

I have been a linux user for more than 20 years, and a Debian user for a good 15 years now. For the first time, I feel like something is off. systemd feels like a Frankenstein that does not belong. It makes the system feel brittle and vulnerable.

Perhaps some more reading is in order. But I am also starting to look into things like Devuan.

Thoughts? Interesting takes and links?

ICYMI: Koen Vervloesem shows you how to run rootless Podman containers and seamlessly integrate them into systemd services
https://www.admin-magazine.com/Archive/2025/85/Run-rootless-Podman-containers-as-systemd-services?utm_source=mam
#Podman #containers #systemd #Docker #Quadlet #Linux

You know it's true, don't even try to protest.

(And hey, having a venom symbiote could be kinda fun, who am I to judge?!?)