Hurray, systemd-resolved is back in Debian.
https://metadata.ftp-master.debian.org/changelogs//main/s/systemd/systemd_257.4-9_changelog
Hurray, systemd-resolved is back in Debian.
https://metadata.ftp-master.debian.org/changelogs//main/s/systemd/systemd_257.4-9_changelog
Huh. Now that I have #otel traces on a bunch of things at home, it's pretty clear that my clocks aren't in sync on every system. They're maybe 1ms off, but it's enough that supposedly-nested trace spans aren't quite nested right.
Which is annoying since I have two local GPS #NTP receivers.
The two "bad" machines were using #systemd-timesyncd to talk to Ubuntu's pool clocks instead of the local clocks. The "good" machines are using #chrony and claim that they're ~2 us off of GPS time.
Now I'm curious -- is this a problem with network latency and Ubuntu's pool, or is that just as good as timesyncd gets?
EDIT: J'ai trouvé cet article et j'ai compris et ça marche https://mo8it.com/blog/quadlet/
S'il y a des gens qui utilisent podman par ici j'ai une question parce que je comprends pas bien la doc.
J'ai un petit container sans root que je lance à la main avec podman start mon_container
quand j'en ai besoin et ça commence à devenir un peu redondant vu que je vais souvent sur mon ordi spécifiquement pour l'utiliser. Donc je cherche à le lancer quand j'ouvre ma session.
J'ai voulu générer une unit systemd avec la commande qui va bien mais j'ai vu qu'elle était dépréciée et qu'il était conseillé d'utiliser un "Quadlet" pour faire ça.
Sauf que mon cerveau percute pas du tout la doc officielle. C'est quoi un quadlet ? Comment je transforme mon container en quadlet ? Et comment je lance le quadlet au démarrage de ma session ?
Je prend toute explication/tuto écrit/tuto vidéo !
Good news, for me, personally . Looks like a bit of an ugly process to get there; but, it's important to see how the sausage is made I guess.
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/289
#Debian #systemd maintainer today removed both systemd-resolved and systemd-nspawn packages from Testing/Trixie/Debian 13 - soon to be in feature freeze - due to disagreements with the Technical Committee. New installs can use resolvconf. https://tracker.debian.org/news/1632477/accepted-systemd-2574-4-source-into-unstable/
systemd-resolved is disappearing in #Debian:
"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)"
https://tracker.debian.org/news/1632477/accepted-systemd-2574-4-source-into-unstable/
Bloody love computers.
Imagine being forbidden from scheduling a shutdown on your very own computer.
What kind of decisions led to this horrid mistake to happen?!
Un po' una guida sulla scelta della propria distro preferita, un po' consigli di filtraggio su DistroWatch, un po' minimalismo. Non manca niente.
Converting my dev laptop to https://devuan.org/ - Debian fork minus systemd.
Going well so far...
Deal a lot with systemd, so wrote a VSCode extension to observe the state of services.
https://github.com/gbraad-vscode/vscode-systemd-manager
It is at a very early devel; it shows all units and their state, you can start/stop/restart and see status. I would like to do daemon-reloads, auto reloading status/follow, filter for service, sort by state, mask, unmask, etc.
I use this over code serve-web, to help with remote management of services. WDYT?
Edit: new image to be more readable at a small size
I wonder why systemd-sysv-generator is deprecated for removal.
I mean, it's not particularly consequential—it's a separate program and can therefore be forked if anyone still cares about it—but what's the point of dropping it?
Is it burdensome on the #systemd maintainers somehow? Pretty hard to imagine, seeing as how the LSB specification is frozen and the systemd unit specification is guaranteed backward compatible.
A #systemd thing I just discovered: I was having problems with a service starting on boot before the disk that had the data for it was mounted, and so it'd get upset about missing files and I'd have to manually fix it. I found that systemd has a `RequiresMountsFor=` option, so I can say `RequiresMountsFor=/mnt/path` and the service won't start until that path has been mounted. Simple, handy, and took a surprising amount of searching to find that (for some reason depending on the unit for the mount itself just didn't work.)
With how extra systemd is in general, how does bootctl (from systemd-boot) not have an option for modifying kernel boot parameters?!
Just trying to find the right, persistent, way of making Plymouth show a boot splash. More digging…
La semaine commence de façon bien ironique quand on se prend la tête avec systemd au même moment où je tombe sur cet article: https://it-notes.dragas.net/2025/03/23/osday-2025-why-choose-bsd-in-2025/
Quadlet: Running Podman containers under systemd
@JdeBP @cstross @RefurioAnachro @Quixoticgeek
You've heard of #GUIX ? No #systemd there.
The whole system is lisp.
#linux #gnu