Wahrscheinlich hat #fefe ein Angebot von Microsoft bekommen, dass er nicht ablehnen konnte.
Systemd-KI mit #poettering oder so.
Wahrscheinlich hat #fefe ein Angebot von Microsoft bekommen, dass er nicht ablehnen konnte.
Systemd-KI mit #poettering oder so.
@joel I mean, #SystemD wasn't done by #Poettering because he had no hobbies - far from it.
SystemD, like #Wayland and #PipeWire is a "necessary evil" because the preexisting solutions are slow, not adaptive, cumbersome or just don't work well at all (i.e. mixed (#DPI & #HiDPI) screens with #X11 are just broken!
Crazy.
Ich bin ja gespannt, was sich in Zukunft etablieren wird.
Poettering hat sich schon 2014 dazu Gedanken gemacht, als das klassische Paketsystem an seine Grenzen stiess (Revisiting How We Put Together Linux Systems), was schlussendlich zur Verbreitung der schrecklichen Flatpak- und ähnlicher Containerredundanz geführt hat.
Kürzlich hat er ein weiteres Essay veröffentlicht (Fitting Everything Together):
Lennart #Poettering is a sadist, and #systemd users are obviously masochists ️
@debacle @zakiuem @disabled @gamercat @ubuntu #Devuan is just a #hategrooming bubble against #Poettering.
#systemd is just their pretext to do so.
I just think that Devuan is an utter waste if time and personnel hours.that could've been spent way better on making #Linux generally better...
Cuz I've yet to see anyone wanting #SystemVinit back.
Not even #Oracle / #Sun want it in #Solaris (#SMF) nor #Apple in #macOS (#LaunchD)...
Ich hab's doch immer geahnt - der #Poettering ist ein Maulwurf von #Microsoft, der #Linux zugrunde richten sollte:
Considering that most major #linux distros (corporate or not) are #Microsoft's direct competitors in the server market; does that not make it more than a little awkward that #Poettering is going to be both a Microsoft employee and the chief developer on #systemd ?
I know Microsoft is no stranger to hiring existing FLOSS devs. But systemd is a pretty major bit of system level middleware that is ever absorbing more of the linux stack, right?
What I missed the first time around, but got alerted* to due to various links in /dev/ not working or set up (properly).
From #Poettering's comment I referenced earlier:
"pid 1 sets up those extra /dev symlinks"
So it's not udev which manages /dev/ but pid 1 ... well ... at least partly.
*) From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975017#46 :
"You might want to just fork udev while it still sort of works outside systemd."
Michael Biebl asking Ben Hutchings to weigh in on the discussion ... that's something else
Who could possibly have foreseen this happening?
"if people want to use udev from other init systems they should do this on their own"
#Poettering claiming "do one thing and do it well" is peak irony
https://github.com/systemd/systemd/commit/6b2229c6c60d0486#commitcomment-42656968
IOW, systemd is now a hard requirement for udev.
I already ran into this on my server, bc "Predictable Network Interface Names" became unpredictable and the udev rule started behaving erratic.
Various issues in systemd's own repo and #Debian is also a victim.
Systemd: Lennart Poettering möchte das Home-Verzeichnis modernisieren | heise online
https://www.heise.de/newsticker/meldung/Systemd-Lennart-Poettering-moechte-das-Home-Verzeichnis-modernisieren-4536581.html