mastodon.online is one of the many independent Mastodon servers you can use to participate in the fediverse.
A newer server operated by the Mastodon gGmbH non-profit

Server stats:

11K
active users

#systemd

12 posts12 participants1 post today
Lobsters<p>My Way to Remove Linuxisms from FreeBSD <a href="https://lobste.rs/s/njhsdh" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">lobste.rs/s/njhsdh</span><span class="invisible"></span></a> <a href="https://mastodon.social/tags/freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freebsd</span></a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a><br><a href="https://eugene-andrienko.com/en/it/2025/03/30/freebsd-pkgs-wout-unwanted-deps" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">eugene-andrienko.com/en/it/202</span><span class="invisible">5/03/30/freebsd-pkgs-wout-unwanted-deps</span></a></p>
Morten Linderud<p>So, we did a thing.</p><p><a href="https://github.com/systemd/systemd/pull/36914" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/systemd/systemd/pul</span><span class="invisible">l/36914</span></a></p><p><a href="https://chaos.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> <a href="https://chaos.social/tags/golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>golang</span></a> <a href="https://chaos.social/tags/go" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>go</span></a> <a href="https://chaos.social/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rust</span></a></p>
Charlie<p>Just wrapped up a revamp of the <a href="https://social.veraciousnetwork.com/tags/Palworld" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Palworld</span></a> <a href="https://social.veraciousnetwork.com/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> installation script for dedicated servers, now with inclusion of a management interface and Discord notification support!</p><p><a href="https://github.com/VeraciousNetwork/Palworld-Linux" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/VeraciousNetwork/Pa</span><span class="invisible">lworld-Linux</span></a></p><p>Tested on <a href="https://social.veraciousnetwork.com/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debian</span></a> but probably works on other platforms. Management interface written in <a href="https://social.veraciousnetwork.com/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a> and fully integrated with <a href="https://social.veraciousnetwork.com/tags/Systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Systemd</span></a></p>
uhurunot the first : <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101532" rel="nofollow noopener" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101532</a> :)<br><br>you might want to revert to an earlier systemd-resolved version and pin it, till <a href="https://snac.el-hoyo.net/social?t=systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> <a href="https://snac.el-hoyo.net/social?t=drama" class="mention hashtag" rel="nofollow noopener" target="_blank">#drama</a> unfolds.. (or just use a better alternative?)<br>
:sigil: Lou Lüeder<p>EDIT: J'ai trouvé cet article et j'ai compris et ça marche 😊 <a href="https://mo8it.com/blog/quadlet/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">mo8it.com/blog/quadlet/</span><span class="invisible"></span></a></p><p>S'il y a des gens qui utilisent podman par ici j'ai une question parce que je comprends pas bien la doc.</p><p>J'ai un petit container sans root que je lance à la main avec <code>podman start mon_container</code> 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.</p><p>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.</p><p>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 ?</p><p>Je prend toute explication/tuto écrit/tuto vidéo !</p><p><a href="https://eldritch.cafe/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podman</span></a> <a href="https://eldritch.cafe/tags/quadlet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>quadlet</span></a> <a href="https://eldritch.cafe/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a></p>
asmw<p>Huh, thanks <span class="h-card" translate="no"><a href="https://mastodon.online/@mullvadnet" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>mullvadnet</span></a></span>!<br>Created an account and added funds in less than 5 minutes and had <a href="https://infosec.exchange/tags/Ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ipv6</span></a> connectivity.</p><p>I think a <a href="https://infosec.exchange/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> update broke something with my <a href="https://infosec.exchange/tags/wireguard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wireguard</span></a> tunnels or routing/port forwarding on the proxy server?</p><p>Not in the mood to debug, rebooting fixed the problem.</p>
KaiXinI might as well be the first few to be affected the recently dropped systemd-resolved.service in <a href="https://snac.bsd.cafe?t=debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a>. I daily use <a href="https://snac.bsd.cafe?t=debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> sid and as a part of today's update, systemd-resolved.service was removed. I had to systemctl restart systemd-resolved.service every time I use VPN to connect to workplace network, which stopped working after the removal, reporting DNS resolution failure. I had to remove the softlinked /etc/resolv.conf to /run/systemd/resolve/resolv.conf and manually add some entries according to the content of /run/systemd/resolve/resolv.conf and restart network services. Thank god <code>/run/systemd/resolve/resolv.conf</code> was still there. <a href="https://snac.bsd.cafe?t=foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://snac.bsd.cafe?t=systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a><br>
Kevin Bowen :xfce:<p><span class="h-card" translate="no"><a href="https://gnu.gl/@wtfismyip" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>wtfismyip</span></a></span> </p><p>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. 😕 </p><p><a href="https://salsa.debian.org/systemd-team/systemd/-/merge_requests/289" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">salsa.debian.org/systemd-team/</span><span class="invisible">systemd/-/merge_requests/289</span></a></p><p><a href="https://fosstodon.org/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debian</span></a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://fosstodon.org/tags/SystemD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SystemD</span></a></p>
st1nger :unverified: 🏴‍☠️ :linux: :freebsd:<p><a href="https://infosec.exchange/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debian</span></a> <a href="https://infosec.exchange/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> 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. <a href="https://tracker.debian.org/news/1632477/accepted-systemd-2574-4-source-into-unstable/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">tracker.debian.org/news/163247</span><span class="invisible">7/accepted-systemd-2574-4-source-into-unstable/</span></a></p>
wtfismyip<p>From Debian Unstable changelog:</p><p>systemd-resolved is going away!</p><p><a href="https://gnu.gl/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debian</span></a> <a href="https://gnu.gl/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://gnu.gl/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a></p>
mika<p>systemd-resolved is disappearing in <a href="https://graz.social/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debian</span></a>:</p><p>"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:<br><a href="https://salsa.debian.org/systemd-team/systemd/-/merge_requests/289" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">salsa.debian.org/systemd-team/</span><span class="invisible">systemd/-/merge_requests/289</span></a><br>(Closes: #1098914)"</p><p><a href="https://tracker.debian.org/news/1632477/accepted-systemd-2574-4-source-into-unstable/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">tracker.debian.org/news/163247</span><span class="invisible">7/accepted-systemd-2574-4-source-into-unstable/</span></a> </p><p><a href="https://graz.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a></p>
ZanaGB<p>Bloody love computers.</p><p>Imagine being forbidden from scheduling a shutdown on your very own computer.</p><p>What kind of decisions led to this horrid mistake to happen?!</p><p><a href="https://mastodon.social/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fedora</span></a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://mastodon.social/tags/rant" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rant</span></a> <a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a></p>
DajeLinux :linux:<p>Un po' una guida sulla scelta della propria distro preferita, un po' consigli di filtraggio su DistroWatch, un po' minimalismo. Non manca niente.</p><p><a href="https://dajelinux.it/archivio/scegliere-distribuzione-linux/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dajelinux.it/archivio/sceglier</span><span class="invisible">e-distribuzione-linux/</span></a></p><p><a href="https://mastodon.uno/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://mastodon.uno/tags/unolinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unolinux</span></a> <a href="https://mastodon.uno/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unix</span></a> <a href="https://mastodon.uno/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> <a href="https://mastodon.uno/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>foss</span></a> <a href="https://mastodon.uno/tags/floss" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>floss</span></a> <a href="https://mastodon.uno/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>debian</span></a> <a href="https://mastodon.uno/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fedora</span></a> <a href="https://mastodon.uno/tags/archlinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>archlinux</span></a> <a href="https://mastodon.uno/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a></p>
Philipp :emacs: :nixos:<p>Is there a "user-oriented" version of <a href="https://fosstodon.org/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> that one can use on servers? We have this hardware controls framework that has a tool to graphically see all the device servers running and restart them with a right click → restart. That'd be cool, but for systemd services. <a href="https://fosstodon.org/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a></p>
Paul Campbell<p>Converting my dev laptop to <a href="https://devuan.org/" rel="nofollow noopener" target="_blank">https://devuan.org/</a> - Debian fork minus systemd.</p><p>Going well so far...</p><p><a class="hashtag" href="https://mitra.kemitix.net/collections/tags/debian" rel="nofollow noopener" target="_blank">#debian</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/devuan" rel="nofollow noopener" target="_blank">#devuan</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/systemd" rel="nofollow noopener" target="_blank">#systemd</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/linux" rel="nofollow noopener" target="_blank">#linux</a></p>
Gerard Braad<p>Deal a lot with systemd, so wrote a VSCode extension to observe the state of services.</p><p><a href="https://github.com/gbraad-vscode/vscode-systemd-manager" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/gbraad-vscode/vscod</span><span class="invisible">e-systemd-manager</span></a></p><p>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.</p><p>I use this over code serve-web, to help with remote management of services. WDYT?</p><p><a href="https://mastodon.social/tags/vscode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vscode</span></a> <a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a></p><p>Edit: new image to be more readable at a small size</p>
argv minus one<p>I wonder why systemd-sysv-generator is deprecated for removal.</p><p>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?</p><p>Is it burdensome on the <a href="https://mastodon.sdf.org/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> maintainers somehow? Pretty hard to imagine, seeing as how the LSB specification is frozen and the systemd unit specification is guaranteed backward compatible.</p>
Robin<p>A <a href="https://teh.entar.net/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> 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.)</p>
Morten Linderud<p>So, guys.</p><p>How much further do I take this?</p><p><a href="https://chaos.social/tags/golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>golang</span></a> <a href="https://chaos.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> <a href="https://chaos.social/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rust</span></a></p>
Gea-Suan Lin<p>在 command line 等 network-online.target 成功後再繼續執行</p><p>INN 看起來會在啟動的時候讀 /etc/resolv.conf 決定 DNS server,但我的機器是 PPPoE 取得網路資訊,在 user cron 用下面的方式跑會造成啟動的時候讀到空的 resolv.conf: @reboot ~/bin/rc.news &gt; /dev/null 2&gt;&amp;1 這會導致後續在接受時的 DNS 反解會失敗... 在不改 code 的前提下,第一個想到的方法是直接寫死 DNS servers (像是 168.95.192.1 + 168.95.1.1),但感覺不太好... 後來想到的解法是改用 systemd 的 Wants= 與 After=,在 ne…</p><p><a href="https://blog.gslin.org/archives/2025/03/25/12320/%e5%9c%a8-command-line-%e7%ad%89-network-online-target-%e6%88%90%e5%8a%9f%e5%be%8c%e5%86%8d%e7%b9%bc%e7%ba%8c%e5%9f%b7%e8%a1%8c/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.gslin.org/archives/2025/0</span><span class="invisible">3/25/12320/%e5%9c%a8-command-line-%e7%ad%89-network-online-target-%e6%88%90%e5%8a%9f%e5%be%8c%e5%86%8d%e7%b9%bc%e7%ba%8c%e5%9f%b7%e8%a1%8c/</span></a></p><p><a href="https://abpe.org/tags/cli" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cli</span></a> <a href="https://abpe.org/tags/command" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>command</span></a> <a href="https://abpe.org/tags/interface" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>interface</span></a> <a href="https://abpe.org/tags/line" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>line</span></a> <a href="https://abpe.org/tags/network" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>network</span></a> <a href="https://abpe.org/tags/online" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>online</span></a> <a href="https://abpe.org/tags/script" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>script</span></a> <a href="https://abpe.org/tags/shell" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>shell</span></a> <a href="https://abpe.org/tags/systemctl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemctl</span></a> <a href="https://abpe.org/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> <a href="https://abpe.org/tags/target" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>target</span></a></p>