We have an all-star list of special guests from out of town, and a packed agenda. If you want to help build the future of image-based OSes, mainline Linux phones, local-first, and more then get your tickets now add yourself to the pad: https://pad.gnome.org/1EIXiLe8Ri2St_ayB8uRHg
Like last time, we also have some lightning talk slots, and on Saturday night there's live music by the one and only
@jimmac! The hype is real 🔥
@zbyszek, a #systemd developer and #Fedora maintainer, will explore the future of image-based, immutable, cryptographically verified #Linux installations, covering engineering challenges, secure updating/extending, and how tools like #mkosi build installation images, initrds, and extensions from distro packages.
Na grafice znajduje się zdjęcie Zbigniewa Jędrzejewskiego-Szmeka, systemowego dewelopera i maintenera Fedory. Obok jego zdjęcia widnieje napis "Image-based Linux with systemd". U dołu grafiki umieszczono informacje o konferencji "Jesień Linuksowa", która odbędzie się w dniach 24-26 października 2025 roku w Hotelu przy Młynie w Rybniku.
@mcc
@ariadne If I could name just one irritating thing about #systemd it's the "external" unit generators that are compiled binaries instead of scripts, I get it's faster but when I came across them I wished I could just test them or modify them on the spot.
Other than that it's a learning curve, but I found it sufficiently customisable to fix any issues or implement any service or device fix-up I ever needed. It even manage my user services now (managed and running under my own UID).
"Digitale Souveränität für Deutschland und Europa ist möglich!" Unter dieser Überschrift hat unsere BSI-Präsidentin einen offenen Brief der Open Source Business Alliance [email protected] erhalten.
@bsi gibt es zur Doppelstrategie noch konkreteres zum Absichern von Software von z.B. US Anbietern? Bin da sowohl aus dem Netzpolitik, Heise und der offenen Antwort immernoch nicht ganz schlau draus geworden.
I’ve never looked at systemd doc before, but honestly, this is pretty fabulous as far as documentation goes. Generally, technical documentation has improved by leaps and bounds since the 80s. I’m excited GNOME is going to depend on systemd’s userdb. Is that weird? https://systemd.io/USER_RECORD/#linux#gnome#systemd
It didn't replace van Smoorenberg init+rc. It replaced Upstart. The existence of Upstart is the part of history that many people forget or gloss over.
van Smoorenberg init+rc always was a straw man. The Debian committee included it, but everyone acknowledged at the time that the main contenders were systemd, Upstart, and OpenRC.
I'm getting the itch of building my next linux install using #systemd#confext and #sysext. 😎
Basic point, memory of #ansible keeps getting further. 😅 Can build out #btrfs subvolumes that are mounted read only. No modification of the /usr or even /etc necessary.
Insecure defaults can lead to surprises. When creating FIFO sockets with systemd, be sure to note that SocketMode defaults to 0666 - that is world readable and writable. That is: any local user can communicate with the FIFO. If your FIFO is used to perform privileged operations you must ensure that either the FIFO file itself is located in secured location or set SocketMode to stricter value.
I spotted one such insecure use in cloud-init: the hotplug FIFO was world writable. This is CVE-2024-11584 and fixed in cloud-init 25.1.3.
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.
A bunch of postmarketOS devices all running Phosh with default postmarketOS wallpaper and the same set of apps installed. From left to right:
* PinePhone Pro
* OnePlus 6T
* Xiaomi Poco F1
* Google Pixel 3a
* OnePlus 6
* Xiaomi Pad 5 Pro
* PinePhone (in the front of the other devices)
@gamingonlinux I would have tested it, but this far it's been deeply depending on #systemd which I think it's wrong way to go, as there are multiple init system and not the #unlx
way of doing things, posrting getting nasty as say BSD don't use systemd at all.
Alright, stupid question for my #Linux friends. I’ve got a cloud instance running Ubuntu 22.04 where a script in the initramfs is bringing up the NIC with DHCPv4 only, and marking it as critical. Because of this, I can’t seem to make #systemd -networkd reload the configuration to bring up a secondary IPv4 address nor the two IPv6 addresses. How would y’all solve this?
Job Interviewer: Describe your process for troubleshooting a network issue.
Sysadmin candidate: First, I check if it's DNS.
Second, I check if it's DNS.
Third, I check if it's still DNS.
If it's not DNS, then it's a cosmic ray.