#systemd

quetzop1@diasp.org

Systemd Creator Lands At Microsoft

Yesterday's surprise was that Lennart Poettering quietly had left Red Hat following a decade and a half there leading PulseAudio among other projects and ultimately going on to start systemd that has fundamentally reshaped modern Linux distributions. It turns out he had joined Microsoft and continuing his work on systemd.

https://www.phoronix.com/scan.php?page=news_item&px=Systemd-Creator-Microsoft

So, the much-hated creator of the much-hated systemd joins the much-hated company Microsoft. How fitting.

#systemd #linux #microsoft #news

diane_a@diasp.org

"When you install a Linux system its just a bunch of RPM or DEB packages. For example of you install CentOS 7.8 Minimal variant you end up with several hundred RPM packages installed. After a week or month many of these packages will get updates sometimes making this CentOS system unusable or even unbootable (recent GRUB Boothole problem for example). On the contrary FreeBSD comes with a Base System concept. This means that when you install FreeBSD you install a minimal system as a whole. No packages or subsystems to be separately updated. Just whole Base System. That means that /boot /bin /sbin /usr /etc /lib /libexec /rescue directories are untouchable by any packages. When you decide to install packages (or build them using FreeBSD Ports) they will all fall into the /usr/local prefix. That means /usr/local/etc for configuration. The /usr/local/bin and /usr/local/sbin directories for binaries. The /usr/local/lib and /usr/local/libexec for libraries and so on. The FreeBSD Base System kernel modules are kept in the same dir along with the kernel in the /boot/kernel directory. To make things tidy all kernel modules that are provided by packages go into the /boot/modules dir. Everything has its place and its separated."

All this quickly became lost when #systemD from #Redhat aggressively took over...

https://vermaden.wordpress.com/2020/09/07/quare-freebsd/

#FreeBSD #Linux #systemD

katzenjens@pod.tchncs.de

#systemd anstatt #cron

Man muss sich ja auch mal in etwas neues einarbeiten. Es ist noch gar nicht so lange her, da war systemd der Inbegriff alles Bösen. Und inzwischen hat man es nicht nur akzeptiert, sondern man nutzt es sogar für seine eigenen Zwecke.

So wie ich das verstanden habe, ist Cron inzwischen eh nur noch ein Stub zu systemd. Dann kann man es auch gleich damit erschlagen. Aufgefallen ist es mir letztens, als ich für Letsencrypt installiert hatte und keinen cronjob für die Zertifikatserneuerung gefunden hatte. Stattdessen war der Kram tatsächlich in systemd abgebildet.

Nun muss ich nur mal sehen, ob mein krudes bash und Python Gewurschtel auch damit funktioniert.
https://www.youtube.com/watch?v=DixhIrgMy3M
#linux #basics

roland@f.haeder.net

I'm done with systemd because it sucks

I have to much issues with #systemd that I'm willing to continue, here are the 2 major ones:

1) On system startup, I don't see all the starting daemons anymore, just until #initrd is finished and then nothing more until #LightDM starts and the graphical UI comes up

2) Console output is no more scrolling down. Maybe this is the reason for 1) here. So this is what happens: I have to execute a small shell script to decrypt and mount my /home directory. It will mount an USB stick and uses #GnuPG to ask me for a passphrase which decrypts a symmetric key stored on that USB stick (backed up on 2 other sticks). Then it will decrypt the #LUKS device which contains my /home directory. It will also start a filesystem check prior mounting it to /home with fsck.ext4 -yv /dev/mapper/home. For this it outputs messages I actually need to see if all went smooth. SystemD seem to have a bug here that prevents it from showing (no scrolling text). I have to switch consoles e.g. with ALT+F1/F2 and the output is shown again.

This really sucks as this way, I cannot properly maintain my #Linux system. I'm now migrating to #Devuan which is free of systemd and which provides the previous old-but-working #sysvinit . So, goodbye #Debian /systemd and hello Devuan/sysvinit!

schestowitz@joindiaspora.com

"We should try to be empathetic toward software maintainers, including those from #systemd and #polkit , so writing inflammatory posts blaming systemd or its maintainers for polkit does not really help to fix the problems that made this a useful security vulnerability." #twitter is a "thing"? https://ariadne.space/2022/01/27/cve-2021-4034/