Dear #BSD / #Anti_SystemD peeps,

Please make friends with #Linux-only, #Systemd fans.

#X114EVR peeps, please make friends with #Wayland fans.

The only way the community at large moves forward is to keep conflict within the domain of friendship. That way we can hold our differences, and learn to synthesize the disagreements.

And please, please don't assume that someone is your ally just because they agree with you on one technical point. I don't have a problem with X11 being maintained until the end of time, I just don't want it to be led by someone with really horrible/destructive politics.

It's not #CancelCulture, it's mercy. I would like to see a destructive ideology "canceled," but people are never my enemy.

Edit: minor re-phrasing of last paragraph

Saw a comment on The Register praising FreeBSD because "no systemd", that isn't something to be proud of lol. I really do not get the whole contempt towards systemd. Just seems like people unwilling to accept change to me.

It works for me so why should I bother changing what works? Hell, systemd has been more reliable for me than Wayland (though that's apples to oranges - you get the idea, tho.)

The "systemctl soft-reboot" #systemd command is so cool
https://www.freedesktop.org/software/systemd/man/latest/systemd-soft-reboot.service.html

Finally a clean way to rapidly re-start everything other than the #Linux kernel… for me, it is extremely useful to be able to do that after applying desktop & graphics stack updates, and to be able to log back in within 10 seconds.

Throwing the idea out here: it would be very nice if someone figured out a way to write a #GNOMEShell extension to provide "Soft reboot" as an alternative to cold reboot!

Some big changes are coming in the @mxlinux 25 release
https://www.linux-magazine.com/Online/News/Upcoming-Changes-for-MXLinux?utm_source=mlm
#Linux #MXLinux #FOSS #Wayland #Plasma #OpenSource #OperatingSystem #distro #Xfce #systemd #SysVinit

Holy hell, the #systemd documentation is a giant rat's nest.

Someone needs to come up with a user-friendly program for creating .service files.

I can't handle having to mentally overlay several man pages in order to get the full picture.

Also, I hate hate hate that it uses a conversational style for describing things that should be bulleted lists, forcing me to parse several words into each paragraph to find the actual option name being described.

What a goddamned mess.

I don't mean to kick off a whole systemd discussion, but there's something very wrong with a system that has to tell you, on the command line, where to look for logs when things don't work as expected.

Job for systemctl status whatever.service" and "journalctl -xeuted with error code.
See "systemctl status whatever.service" and "journalctl -xeu whatever.service" for details.

From #transactional-updates to #systemd-pull integration with #OBS, learn how #openSUSE is shaping the future of #immutable and rolling systems from this #oSC25 talk. #MicroOS #Tumbleweed #OpenSource https://youtu.be/MPMrlUj1sVA?si=bMjxsJtyIOEyqzgb

https://roguesecurity.dev/blog/systemd-hardening

Another #selfhosting blog down, this time some casual notes on #systemd #security. Love it or hate it, systemd is a big player in the bulk of Linux systems out there, and these are a few notes on how to lock down some of the defaults.

How to install #Debian 13 #Trixie with #runit instead of #systemd

* Boot the "netinstall" medium and do normal text-based installation
* At "Software selection" deselect all options
* After "Finishing the installation" DON't choose "Continue".Choose "Go back"
* Select "Execute a shell" and "Continue"
* At the shell enter "chroot /target"
* Enter "apt --allow-remove-essential install runit runit-init rsyslog systemd- sysv-systemd- init-" (the dashes after the last 3 packages are important)
* Hit Return
* Enter "exit"
* Back in the Debian installer main menu choose "Finish the installation" and then "Continue"
* reboot and login
* Create a file /etc/apt/preferences.d/systemd with the content:
Package: systemd
Pin: release *
Pin-Priority: -1
* execute "apt purge systemd"
* Profit

you ever get an error and have to check the date to make sure it's not April 1st?
#systemd

¿Hiciste cambios en el sistema, o actualizaste, y querés reiniciar?

¿No cambiaron cosas en el núcleo/kernel?

Entonces podés realizar un "soft-reboot", y reiniciar el espacio de usuario solamente, sin reiniciar el sistema completo.

$ sudo systemctl soft-reboot

Disponible en systemd >254

Da willst ne #qemu VM über #Systemd starten und packst den Pfad zur PIDFile in die Service Unit, da schnauzt dich Systemd an die PIDFile sei wegen irgendwas mit Symlink Chain bzw. cgroups nicht akzeptabel??

I've been a silly hobby contrarian for the longest time. It always gives me an inexplicable, warm feeling to do things the unpopular way, to tread untrodden paths.

I play the least popular character type or class in video #games like #FFXIV or #Battlefield. No metagaming and no guides - even for strategy or tycoon games. When I learn what the best starter setup is, I use another. I used subpar #chess openings even while learning.

If possible, I used alternative mod frameworks like #Fabric or #Quilt for #Minecraft. No #systemd and no #Mastodon. I always wanted to use super obscure #Linux distributions and desktop environments.

But there's one exception.

After decades of using and enjoying obscure window managers and desktops, I am a full-on #KDE fan.

And with that context, that's a big compliment. I love KDE. It does everything I want from a desktop. It's the most popular, but I don't care. It's perfect to me.

#NTP. #NTPSEC. #systemd-timesyncd. #chrony. Gibt's irgendwo eine hübsche Gegenüberstellung, wer was (besser) kann?

#systemd never fails to impress:

● homebridge
State: running
Units: 306 loaded (incl. loaded aliases)
Jobs: 0 queued
Failed: 0 units
Since: Wed 1969-12-31 16:00:03 PST; 55 years 7 months ago

And in case you were wondering:

mark@homebridge:~ $ date
Thu Aug 7 07:20:23 PM PDT 2025

I particularly love how Windows boots almost 3 times as fast as Linux now under systemd.

I just thought of

(a) Installing a cron on my NixOS systems.

(b) Setting up cron.monthly, cron.daily, etc., or even cron.15th-of-each-month and so forth.

(c) Timing events by putting scripts in these directories.

(d) Doing all this with the NixOS configuration.

Why?

BECAUSE SYSTEMD IS EVIL!!!!!!!

Systemd is what you get when people are working on this who have never in their lives used Unix, and those who have and care much contribute to BSDs instead.