This is fake news. The article doesn’t provide any evidence that he’s working at Microsoft.
Void trannies paid phoronix to write a hitpiece.
This is fake news. The article doesn’t provide any evidence that he’s working at Microsoft.
Void trannies paid phoronix to write a hitpiece.
he is, but it doesn't matter
microsoft runs one of the biggest linux architectures that exists. Right next to Amazon and google.
If anything with the multi threading of reading HDDs on boot and other things that exponentially speed up the kernel and systemd, it'll be a good thing.
Keep in mind red hat has been owned by IBM for years, which is just as bad as microsoft was in the past, so really irrelevant.
linux bros, we won. Big corp is spending billions to write our software for us.
This may take many by surprise but let's not forget Microsoft has over time employed a number of Linux developers and other prominent open-source developers... Microsoft currently employs Python creator Guido van Rossum, GNOME creator Miguel de Icaza had been employed by Microsoft from 2016 when they acquired Xamarin to earlier this year when he left, Nat Friedman as part of Xamarin-Microsoft served as GitHub CEO following Microsoft's acquisition, Gentoo Linux founder Daniel Robbins was previously employed by Microsoft, Steve French as the Linux CIFS/SMB2/SMB3 maintainer and Samba team member works for Microsoft, and Microsoft employs/previously-employed a large number of upstream Linux developers like Matteo Croce, Matthew Wilcox, Tyler Hicks, Shyam Prasad N, Michael Kelley, and many others beyond just the usual immediately recognizable names to Linux enthusiasts/developers. It was also just earlier this year that Christian Brauner as another longtime Linux kernel developer joined Microsoft. Christian Brauner is Berlin-based like Lennart and moved on to Microsoft after the past half-decade at Canonical working on the Linux kernel, LXC, systemd, and more.
>gentoo
He left ms and made the most "linux" distro after nix precisely because he hated microsoft that much >a bunch of windows-first projects
lol ok >python >gnome >lxc >systemd
lmao
The so-called Linux community is supposed to be "smart" but I see that gets challenged repeatedly.
This "article" is completely unable to provide a singular source of what it claims, unless I missed something here is what it says:
>pottering left redhat (proof is that his RH email is not in use) -> verifiable truth >then the author got messages from random people that he joined MSFT -> ok and? >author says it's true -> 0 (ZERO) evidence >goes on to litter the rest of the article with irrelevant boilerplate
The "linux community" ran with it, which is very astonishing to see. I guess this community is not very smart after-all, or at least the vocal demographic of it.
I can understand IQfy toddlers are highly susceptible to propaganda, but HN, r/linux, google+ people are also blindly trusting an obvious hit piece.
This may take many by surprise but let's not forget Microsoft has over time employed a number of Linux developers and other prominent open-source developers... Microsoft currently employs Python creator Guido van Rossum, GNOME creator Miguel de Icaza had been employed by Microsoft from 2016 when they acquired Xamarin to earlier this year when he left, Nat Friedman as part of Xamarin-Microsoft served as GitHub CEO following Microsoft's acquisition, Gentoo Linux founder Daniel Robbins was previously employed by Microsoft, Steve French as the Linux CIFS/SMB2/SMB3 maintainer and Samba team member works for Microsoft, and Microsoft employs/previously-employed a large number of upstream Linux developers like Matteo Croce, Matthew Wilcox, Tyler Hicks, Shyam Prasad N, Michael Kelley, and many others beyond just the usual immediately recognizable names to Linux enthusiasts/developers. It was also just earlier this year that Christian Brauner as another longtime Linux kernel developer joined Microsoft. Christian Brauner is Berlin-based like Lennart and moved on to Microsoft after the past half-decade at Canonical working on the Linux kernel, LXC, systemd, and more.
This is fake news. The article doesn’t provide any evidence that he’s working at Microsoft.
Void trannies paid phoronix to write a hitpiece.
Lennart and Microsoft could both issue a correction if the article is wrong.
Neither have.
You are coping.
Actually if it was MSFT back in the mid 2000s, they could have sued phoronix but they are trying to maintain a politically correct image.
Microsoft is a trillion dollar company, they are in no rush to "correct the record", neither is Lennart as he hasn't yet disclosed where he's working.
I know that it's difficult to admit that pulseaudio and systemd have been projects created to destroy FOSS from the inside since the beginning after years of shilling them, even when no one even bothers pretending any more and the proof appears right in front of your eyes, but you will have to face the truth someday.
>pulseaudio and systemd
Back in late 2000's Linux was in complete and utter disarray and systemd brought some form of standardization to Linux. Linux without systemd feels like some random BSD and there is no hope for any big time software to be ported to these platforms.
Systemd is going to be very crucial in the days to come when the linux system settings apps are finally able to do anything more than trivial "changing the theme". The reason Windows has a proper control panel is because of the tight integration with the one and only service manager.
>the proof appears right in front of your eyes
what proof, exactly?
>he thinks the init system is relevant to running proprietary software on linux
Actual idiot.
2 years ago
bruce3434
Integration with service manager is very necessary for modern apps. Calls to inhibit, live power scheduling, running in a background process, being invoked from a background process, applying changes at reboot/logins are solved with a good integrated standard service manager. Why would anyone advocate against apps being able to make use of the service manager just to feel special is beyond my understanding.
>Back in late 2000's Linux was in complete and utter disarray and systemd brought some form of standardization to Linux. Linux without systemd feels like some random BSD and there is no hope for any big time software to be ported to these platforms.
Almost all of the "big time" software was both developed AND portable before systemd made init and whatever else init consumed into a monopoly.
you're a real fricking moron and I can't believe you're still trying to justify the unethical practices of those pushing systemd.
>Almost all of the "big time" software was both developed AND portable before systemd
If you really want to see what a Linux without systemd would look like, go use BSD. >unethical practices
What unethical practices? Debian, Ubuntu, Arch, OpenSUSE were never held at a gun point. When you realize standardization is far more important than fragmentation bullcrap, you'd want to adopt systemd.
There is absolutely 0 interoperability between shepherd, runit, upstart or whetever the frick service manager that exist/ed.
2 years ago
bruce3434
>being invoked from a background proces
Should add, being invoked at a certain time or under a condition WITHOUT a separate background process.
2 years ago
Anonymous
>my video games NEED systemd because... uh... they just do okay!
Meanwhile any game that runs on a systemd distro will also run without systemd.
2 years ago
bruce3434
Who said anything about games?
The simplest of the tools need a service manager: like a todo/event scheduling app.
>What unethical practices?
nice digits but you're a waste of oxygen.
I know when your worldview is fundamentally challenged it's hard to argue with logic but you got any arguments?
2 years ago
Anonymous
>calendar applications NEED systemd
You don't even use linux. Actual moron.
2 years ago
bruce3434
Name one non-DE specific calendar app that will invoke an alarm without its own background process. >You don't even use linux.
No YOU don't. You only dualboot/run linux on VM to feel special. Whereas people who use and develop for linux on a day to day basis see the obvious issues that plague the system.
2 years ago
Anonymous
>I NEED systemd to run a process in the background
you don't even know how to code
2 years ago
bruce3434
>Name one non-DE specific calendar app that will invoke an alarm without its own background process. >without its own background process.
Did you think I was going to fall for this trick?
>you don't even know how to code
lmao majority of anti systemd circlejerk (including yourself) don't know anything past hello world.
2 years ago
Anonymous
>he still thinks background processes require systemd
This is by far the most bizarre justification for systemd I've ever heard. It's clear you don't even belong on this board.
2 years ago
bruce3434
Are you suggesting all apps should start their own background process? lmao holy shit IQfy is the dumbest bunch of clowns in the internet.
2 years ago
Anonymous
>I need systemd to daemonize my process because I don't know how to
Read a book.
2 years ago
bruce3434
>read a book
Do tell me what book uncovers the magic of daemonize without relying on either its own process or the system service manager
lmao
So these people complain about systemd. Fricking hilarious I tell you.
2 years ago
bruce3434
>daemonize
daemonizing
>inb4 patch kernel
2 years ago
Anonymous
I don't have time to read a book, because I have work to do. Luckily, systemd just works, and lets me do just that.
2 years ago
Anonymous
Or you could just use cron for your calendar like a white person. Yeah I know cron on Linux systems with systemd is just a part of systemd, but that's not how it's been until recently and definitely not how it should be.
2 years ago
bruce3434
>replace a system daemon with my own shitty daemon that nobody gives a frick about, see it works.. muh hwite man!!
2 years ago
Anonymous
>no argument
2 years ago
bruce3434
What argument? Why the frick would anybody use cron when systemd already does what it does? Why should the end user install cron for you?
2 years ago
Anonymous
>no systemd
You have a lot to learn about computers, anon.
2 years ago
Anonymous
>yeah bro I'll just fork all my daemons myself and reimplement basic service management features in every one of them, in a slightly different way each time of course >yeah bro /bin/kill is a perfectly acceptable daemon control tool >yeah bro having a bunch of disjointed daemons is totally a good idea
Now this is peak unixgay moronation. Go back to your PDP-11.
2 years ago
Anonymous
Disjointedness can be beneficial. Systemd can spaz-out because one sub-process dies and it keeps trying to restart it while logging error messages the entire time until /var is full. And then what do you do? Restart systemd? If that hangs for any reason, you get kernel panic.
2 years ago
Anonymous
>Systemd can spaz-out because one sub-process dies and it keeps trying to restart it while logging error messages the entire time
This is why there is a burst limit on restarts. After a couple of failed restarts in rapid succession, systemd will stop trying to restart a service because it clearly doesn't fix the problem. >until /var is full
This cannot happen because journald has a safety mechanism in place that prevents it from filling up the disk where logs are kept. >And then what do you do?
Assuming the burst limit did not exist, you can still tell systemd explicitly to stop that service, which will make it cease its attempts at restarting it immediately. You then go on to fix whatever causes the daemon to fail to start properly. There is no benefit to disjointed service management.
2 years ago
Anonymous
And if one of those settings is not correct, what is the fallback? I'm not making this shit up just as an intellectual exercise: I've seen enough bug reports filed by people who do not hate systemd about how it can do crazy shit when they are not expecting it at all because some daemon failed to check the right box. There's a reason fault tolerant design does not rely on any one process's decision-tree.
2 years ago
Anonymous
>And if one of those settings is not correct, what is the fallback?
I've already named two points at which the original situation gets mitigated and one third way to stop it manually should one or both of those mechanisms fail. Keep in mind that the default restart policy is to simply not restart, so this entire scenario can only occur if a manual configuration change has already been made, at which point the administrator should be vividly aware that the change he made may cause a problem and be ready to fix it if it occurs. >I've seen enough bug reports
I encourage you to share one.
2 years ago
Anonymous
>I know when your worldview is fundamentally challenged it's hard to argue with logic but you got any arguments?
This is projection, isn't it?
2 years ago
Anonymous
>What unethical practices?
nice digits but you're a waste of oxygen.
>Back in late 2000's Linux was in complete and utter disarray and systemd brought some form of standardization to Linux. Linux without systemd feels like some random BSD and there is no hope for any big time software to be ported to these platforms.
Almost all of the "big time" software was both developed AND portable before systemd made init and whatever else init consumed into a monopoly.
you're a real fricking moron and I can't believe you're still trying to justify the unethical practices of those pushing systemd.
It's all over the news, to those morons denying it. There's a 99% chance it's true.
Finally, systemd found its home where it belongs, at Microsoft. A shitty and invasive piece of software in a shitty and invasive company.
Like poettery.
This is such sweet redemption. I remember the years of systemd fanboys arguing and shillling in favor of a piece of software that spins itself as having no substitutes in a very unfree way.
For years these homosexuals sucked off poettering and systemd.
I hope this is a nice cold shower for those clowns, you don't throw half a centuries worth of wisdom in the trash because you want a new shiny thing.
I hope this is also a lesson for Wayland. Let wayland get developed, choices are good, but stfu about deprecating competing software.
>I hope this is also a lesson for Wayland. Let wayland get developed, choices are good, but stfu about deprecating competing software.
Wayland is already doing serious damage to KDE. KDE devs are introducing new bugs to the X version at an alarming rate because most of them are only using/testing with wayland.
That's the charitable interpretation anyway. It might be intentional sabotage. Best case scenario is that divided attention between wayland and X is responsible for the decline in quality, but it's easy to see how this could be a deliberate effect of wayland.
>Best case scenario is that divided attention between wayland and X is responsible for the decline in quality, but it's easy to see how this could be a deliberate effect of wayland.
I wouldn't be surprised.
>most of them are only using/testing with wayland.
that's pretty irresponsible of the KDE devs considering wayland is by far a minority in % of users.
Cool. Can we now have a slightly less bloated version of systemd that satisfies the neckbeards too?
Can't wrap my head around why is systemd the only project to provide init+process supervision+logging in one nice package.
Microsoft already has had several contributions in the Linux kernel itself for years. This changes nothing.
he is, but it doesn't matter
microsoft runs one of the biggest linux architectures that exists. Right next to Amazon and google.
If anything with the multi threading of reading HDDs on boot and other things that exponentially speed up the kernel and systemd, it'll be a good thing.
Keep in mind red hat has been owned by IBM for years, which is just as bad as microsoft was in the past, so really irrelevant.
linux bros, we won. Big corp is spending billions to write our software for us.
Microsoft can't un-LGPL Systemd.
This is fake news. The article doesn’t provide any evidence that he’s working at Microsoft.
Void trannies paid phoronix to write a hitpiece.
https://www.msn.com/en-us/news/technology/systemd-supremo-lennart-poettering-leaves-red-hat-for-microsoft/ar-AAZk8bh
>Void trannies paid phoronix to write a hitpiece.
rent free
homosexual op is using comic sans as the default font
Did you read the article you posted?
This may take many by surprise but let's not forget Microsoft has over time employed a number of Linux developers and other prominent open-source developers... Microsoft currently employs Python creator Guido van Rossum, GNOME creator Miguel de Icaza had been employed by Microsoft from 2016 when they acquired Xamarin to earlier this year when he left, Nat Friedman as part of Xamarin-Microsoft served as GitHub CEO following Microsoft's acquisition, Gentoo Linux founder Daniel Robbins was previously employed by Microsoft, Steve French as the Linux CIFS/SMB2/SMB3 maintainer and Samba team member works for Microsoft, and Microsoft employs/previously-employed a large number of upstream Linux developers like Matteo Croce, Matthew Wilcox, Tyler Hicks, Shyam Prasad N, Michael Kelley, and many others beyond just the usual immediately recognizable names to Linux enthusiasts/developers. It was also just earlier this year that Christian Brauner as another longtime Linux kernel developer joined Microsoft. Christian Brauner is Berlin-based like Lennart and moved on to Microsoft after the past half-decade at Canonical working on the Linux kernel, LXC, systemd, and more.
No it's different when the guy who finally gave Linux a coherent underlying system does it
>gentoo
He left ms and made the most "linux" distro after nix precisely because he hated microsoft that much
>a bunch of windows-first projects
lol ok
>python
>gnome
>lxc
>systemd
lmao
I just can't why people that work on FOSS linux software suddenly turn 360deg and go work for Microsoft of them all.
Lennart, like Migual de Icaza, always was a snake from the very beginning.
>suddenly turn 360deg
average linux user
>newbie
average Windows user
Working in FOSS doesn't pay 500k$ per year.
At some point your code becomes verbose enough that you can only work at microsoft.
Don't care. Still not installing the shitty alternative you made in python
He's always been an NSA plant. SystemD is the backdoor
The so-called Linux community is supposed to be "smart" but I see that gets challenged repeatedly.
This "article" is completely unable to provide a singular source of what it claims, unless I missed something here is what it says:
>pottering left redhat (proof is that his RH email is not in use) -> verifiable truth
>then the author got messages from random people that he joined MSFT -> ok and?
>author says it's true -> 0 (ZERO) evidence
>goes on to litter the rest of the article with irrelevant boilerplate
The "linux community" ran with it, which is very astonishing to see. I guess this community is not very smart after-all, or at least the vocal demographic of it.
I can understand IQfy toddlers are highly susceptible to propaganda, but HN, r/linux, google+ people are also blindly trusting an obvious hit piece.
Lennart and Microsoft could both issue a correction if the article is wrong.
Neither have.
You are coping.
Actually if it was MSFT back in the mid 2000s, they could have sued phoronix but they are trying to maintain a politically correct image.
Microsoft is a trillion dollar company, they are in no rush to "correct the record", neither is Lennart as he hasn't yet disclosed where he's working.
Cope harder.
I know that it's difficult to admit that pulseaudio and systemd have been projects created to destroy FOSS from the inside since the beginning after years of shilling them, even when no one even bothers pretending any more and the proof appears right in front of your eyes, but you will have to face the truth someday.
>pulseaudio and systemd
Back in late 2000's Linux was in complete and utter disarray and systemd brought some form of standardization to Linux. Linux without systemd feels like some random BSD and there is no hope for any big time software to be ported to these platforms.
Systemd is going to be very crucial in the days to come when the linux system settings apps are finally able to do anything more than trivial "changing the theme". The reason Windows has a proper control panel is because of the tight integration with the one and only service manager.
>the proof appears right in front of your eyes
what proof, exactly?
>he thinks the init system is relevant to running proprietary software on linux
Actual idiot.
Integration with service manager is very necessary for modern apps. Calls to inhibit, live power scheduling, running in a background process, being invoked from a background process, applying changes at reboot/logins are solved with a good integrated standard service manager. Why would anyone advocate against apps being able to make use of the service manager just to feel special is beyond my understanding.
>Almost all of the "big time" software was both developed AND portable before systemd
If you really want to see what a Linux without systemd would look like, go use BSD.
>unethical practices
What unethical practices? Debian, Ubuntu, Arch, OpenSUSE were never held at a gun point. When you realize standardization is far more important than fragmentation bullcrap, you'd want to adopt systemd.
There is absolutely 0 interoperability between shepherd, runit, upstart or whetever the frick service manager that exist/ed.
>being invoked from a background proces
Should add, being invoked at a certain time or under a condition WITHOUT a separate background process.
>my video games NEED systemd because... uh... they just do okay!
Meanwhile any game that runs on a systemd distro will also run without systemd.
Who said anything about games?
The simplest of the tools need a service manager: like a todo/event scheduling app.
I know when your worldview is fundamentally challenged it's hard to argue with logic but you got any arguments?
>calendar applications NEED systemd
You don't even use linux. Actual moron.
Name one non-DE specific calendar app that will invoke an alarm without its own background process.
>You don't even use linux.
No YOU don't. You only dualboot/run linux on VM to feel special. Whereas people who use and develop for linux on a day to day basis see the obvious issues that plague the system.
>I NEED systemd to run a process in the background
you don't even know how to code
>Name one non-DE specific calendar app that will invoke an alarm without its own background process.
>without its own background process.
Did you think I was going to fall for this trick?
>you don't even know how to code
lmao majority of anti systemd circlejerk (including yourself) don't know anything past hello world.
>he still thinks background processes require systemd
This is by far the most bizarre justification for systemd I've ever heard. It's clear you don't even belong on this board.
Are you suggesting all apps should start their own background process? lmao holy shit IQfy is the dumbest bunch of clowns in the internet.
>I need systemd to daemonize my process because I don't know how to
Read a book.
>read a book
Do tell me what book uncovers the magic of daemonize without relying on either its own process or the system service manager
lmao
So these people complain about systemd. Fricking hilarious I tell you.
>daemonize
daemonizing
>inb4 patch kernel
I don't have time to read a book, because I have work to do. Luckily, systemd just works, and lets me do just that.
Or you could just use cron for your calendar like a white person. Yeah I know cron on Linux systems with systemd is just a part of systemd, but that's not how it's been until recently and definitely not how it should be.
>replace a system daemon with my own shitty daemon that nobody gives a frick about, see it works.. muh hwite man!!
>no argument
What argument? Why the frick would anybody use cron when systemd already does what it does? Why should the end user install cron for you?
>no systemd
You have a lot to learn about computers, anon.
>yeah bro I'll just fork all my daemons myself and reimplement basic service management features in every one of them, in a slightly different way each time of course
>yeah bro /bin/kill is a perfectly acceptable daemon control tool
>yeah bro having a bunch of disjointed daemons is totally a good idea
Now this is peak unixgay moronation. Go back to your PDP-11.
Disjointedness can be beneficial. Systemd can spaz-out because one sub-process dies and it keeps trying to restart it while logging error messages the entire time until /var is full. And then what do you do? Restart systemd? If that hangs for any reason, you get kernel panic.
>Systemd can spaz-out because one sub-process dies and it keeps trying to restart it while logging error messages the entire time
This is why there is a burst limit on restarts. After a couple of failed restarts in rapid succession, systemd will stop trying to restart a service because it clearly doesn't fix the problem.
>until /var is full
This cannot happen because journald has a safety mechanism in place that prevents it from filling up the disk where logs are kept.
>And then what do you do?
Assuming the burst limit did not exist, you can still tell systemd explicitly to stop that service, which will make it cease its attempts at restarting it immediately. You then go on to fix whatever causes the daemon to fail to start properly. There is no benefit to disjointed service management.
And if one of those settings is not correct, what is the fallback? I'm not making this shit up just as an intellectual exercise: I've seen enough bug reports filed by people who do not hate systemd about how it can do crazy shit when they are not expecting it at all because some daemon failed to check the right box. There's a reason fault tolerant design does not rely on any one process's decision-tree.
>And if one of those settings is not correct, what is the fallback?
I've already named two points at which the original situation gets mitigated and one third way to stop it manually should one or both of those mechanisms fail. Keep in mind that the default restart policy is to simply not restart, so this entire scenario can only occur if a manual configuration change has already been made, at which point the administrator should be vividly aware that the change he made may cause a problem and be ready to fix it if it occurs.
>I've seen enough bug reports
I encourage you to share one.
>I know when your worldview is fundamentally challenged it's hard to argue with logic but you got any arguments?
This is projection, isn't it?
>What unethical practices?
nice digits but you're a waste of oxygen.
>Back in late 2000's Linux was in complete and utter disarray and systemd brought some form of standardization to Linux. Linux without systemd feels like some random BSD and there is no hope for any big time software to be ported to these platforms.
Almost all of the "big time" software was both developed AND portable before systemd made init and whatever else init consumed into a monopoly.
you're a real fricking moron and I can't believe you're still trying to justify the unethical practices of those pushing systemd.
It's all over the news, to those morons denying it. There's a 99% chance it's true.
Finally, systemd found its home where it belongs, at Microsoft. A shitty and invasive piece of software in a shitty and invasive company.
Like poettery.
This is such sweet redemption. I remember the years of systemd fanboys arguing and shillling in favor of a piece of software that spins itself as having no substitutes in a very unfree way.
For years these homosexuals sucked off poettering and systemd.
I hope this is a nice cold shower for those clowns, you don't throw half a centuries worth of wisdom in the trash because you want a new shiny thing.
I hope this is also a lesson for Wayland. Let wayland get developed, choices are good, but stfu about deprecating competing software.
>I hope this is also a lesson for Wayland. Let wayland get developed, choices are good, but stfu about deprecating competing software.
Wayland is already doing serious damage to KDE. KDE devs are introducing new bugs to the X version at an alarming rate because most of them are only using/testing with wayland.
That's the charitable interpretation anyway. It might be intentional sabotage. Best case scenario is that divided attention between wayland and X is responsible for the decline in quality, but it's easy to see how this could be a deliberate effect of wayland.
>Best case scenario is that divided attention between wayland and X is responsible for the decline in quality, but it's easy to see how this could be a deliberate effect of wayland.
I wouldn't be surprised.
>most of them are only using/testing with wayland.
that's pretty irresponsible of the KDE devs considering wayland is by far a minority in % of users.
Implying I give a frick. As long as it remains FOSS and works, I don't care who funds it.
>Barely-functional monolith that's integrated on the system level and everything else needs to depend on
Systemd was always a Microsoft product.
FINALLY I can get pipewire and systemd and gnome on my Windows 11 install! I literally can't wait!
>now
Always has been
The infiltrating agent is coming back home with the kill switch
>oh noes, someone got a jerb somewhere else!
Cool. Can we now have a slightly less bloated version of systemd that satisfies the neckbeards too?
Can't wrap my head around why is systemd the only project to provide init+process supervision+logging in one nice package.
So are all systemd telemetry pings going to Microsoft now instead of Google?
Does Microsoft even provide a public recursive DNS?
Going to install Artix and that's it. Hope every systemd dicksucking wanker suffers a horrific death along with their families.
>fartix schizo thinks he can escape
Use Void
come da home wite boi
Microsoft is probably impressed that he convinced and bullied the majority of Linux users to install a backdoor.
this meme is stupid