Yes, i hope your view is correct. Indeed he can work for whatever company he likes, but i would see that as a conflict of interest of some kind. Remember also that when you sign up with big tech companies its common that you sell them the intellectual property of all your works, even outside work hours, specially if in the sale related field. Maybe it's not his case, i have no idea.
I was concerned. Maybe i still am a bit. But the fact that systemd can always be forked (or ignored, as that is still possible today) its a comfortable thought.
I don't even use sudo, so i will certainly not use run0. I have nothing against run0, it make even sense if the footprint is actually smaller than sudo. I was only reporting the article posted on telegram, as i have added a note to the original post, i did not share the view reported in the copied text, but i choose to report it verbatim for clarity.
That is true, it's open source after all. But i am maybe too old to remember Microsoft strategies to embrace and extinguish... So i am a bit worried, like i was worried that Magisk would be crippled since the lead dev was hired by Google (and indeed, there have been very few progress on Magisk, with Kernel SU getting all the hype lately).
The risk is that the IP will get banned AFTER you start sending out mail from it because it has zero reputation...
IT happened to me too and it took months, if not years, to get it definitely cleared. And if you neighbour with a similar IP get infected and start spamming, it's all over again. This is the main issue with residential IPs, it's a very real issue.
To get around it, rent a VPS with a non residential IP and front the mail server there, with tunnels (wireguard+nft) back to your home mail server, so at least the public facing IP is good or has less risks or being blacklisted.
Again i am not interested in the technical aspect of systemd, yes i do like handling init scripts (OpenRC, not sysv...) so maybe i am a bit unconventional. The point i was trying to make was about how sustainable is having a core piece of linux that keeps growing managed by IBM and Microsoft, and if this was of concern with anybody else, which seems not to be the case.
Yeah the telegram post that i copied here is indeed pretty polarized against systemd, that's why i reported it integrally because that is not my view, and i think that is dumb to call names microsoft or the like. Still i find it concerning that microsoft and IBM controls somehow systemd and what that means, if it gets even more rooted inside everything in linux.
Jokes apart, well i think that having a core component so much linked to IBM and Microsoft is a potential danger to Linux itself. What if it was the kernel to be in the hands of Google and Microsoft? Where would Linux as we know it be going to?
This is concerning, i think. I thought it was clear from the first post. I dont want to share an opinion on how good or bad systemd is from a technical point of view, because i do not have such an opinion because i use OpenRC and never used systemd long enough to judge it from a tech pov
Probably it's too much asking to go trough all of them indeed, it's lemmy afterall, already most of the comments didnt actually read the entire first post either.
But i think i didnt have to provide "pro-systemd" links as my intent is not to discuss it's technical goodness (which i do not dispute!) but to understand what is the common idea about the fact that systemd could be a critical part of Linux which is in the hands of IBM and Microsoft and what this means for the linux community overall.
Either nobody cares, or it's too much complottistic to be real.
Yes, that is one point. Having the main dev working for "the enemy". Systemd being developed by the main dev who is at microsoft?
To me that rings some bells.
He will keep doing a great job, he is paid for this, but the point is that microsoft could try to control linux a bit too much, and so is IBM...
Shimitar @ Shimitar @downonthestreet.eu Posts 12Comments 464Joined 6 mo. ago
I only used OpenWRT on netgear (arm) hardware... So for x86 I have no idea, but they have great forums you can lurk or inquire...
It should support all WiFi chipsets supported by Linux.