- Joined
- Dec 28, 2014
Can he really be worse than a Microsoft operative whose sole motive seems to be that everything is wrong with Linux and it needs to be fixed by making it more like Windows?
Diseased Open Source Software Community - it's about ethics in Code of Conducts
- Thread starter CrunkLord420
- Start date
-
🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
- Joined
- Aug 28, 2015
I don't understand how much traction Lennart gets, especially when it blatantly seems to be the coder version of Stephen Elop.
polyester
kiwifarms.net
- Joined
- Jan 26, 2020
I'm gonna go against the grain here, and say that Poettering doesn't deserve all this hate, and his systemd is a marked improvement over Linux's previous init systems.
As I understand it, the old init systems consisted of mountains of shell-script spaghetti-code held together by duct tape, with each Linux distro maintaining its own patches that hacked in their distro-specific start-up services (like network managers) in a way that could easily break when upstream made changes to those scripts, and made booting Linux machines slow mostly due to the impossibility of parallelizing that whole mess.
Whereas systemd offers a proper, clean way to define boot steps / start-up services and dependencies between them, and automatically loads them in the correct order, with as much parallelization as possible, and each immediately following its dependencies (like a network manager getting started as soon as the network interface comes online).
The distros now don't need custom patches for the init system itself, they can just define additional services using the standardized format provided by systemd, to automatically get loaded at the correct time.
Poettering made enemies out of other open source fags by being rude and dismissive of their code, but they should just suck it up and compete with better software rather than with whining.
At least in the cases of systemd and PulseAudio IMO, Poettering was right in identifying an outdated mess that needed a properly-engineered solution but everyone kinda ignored it because they didn't want to bother sitting down and creating a well-thought-out one from scratch, so he just did it. And I think that deserves respect.
As I understand it, the old init systems consisted of mountains of shell-script spaghetti-code held together by duct tape, with each Linux distro maintaining its own patches that hacked in their distro-specific start-up services (like network managers) in a way that could easily break when upstream made changes to those scripts, and made booting Linux machines slow mostly due to the impossibility of parallelizing that whole mess.
Whereas systemd offers a proper, clean way to define boot steps / start-up services and dependencies between them, and automatically loads them in the correct order, with as much parallelization as possible, and each immediately following its dependencies (like a network manager getting started as soon as the network interface comes online).
The distros now don't need custom patches for the init system itself, they can just define additional services using the standardized format provided by systemd, to automatically get loaded at the correct time.
Poettering made enemies out of other open source fags by being rude and dismissive of their code, but they should just suck it up and compete with better software rather than with whining.
At least in the cases of systemd and PulseAudio IMO, Poettering was right in identifying an outdated mess that needed a properly-engineered solution but everyone kinda ignored it because they didn't want to bother sitting down and creating a well-thought-out one from scratch, so he just did it. And I think that deserves respect.
- Joined
- May 9, 2017
systemd is the communism of Linux boot systems: Mostly correct in its identification of the problems, but somehow managed to replace it with another set of problems that are a hundred times times worse. In this case, systemd has become a bloated monolithic blob governing a bunch of unrelated subsystems. On top of that a lot of important packages mysteriously developed hard dependencies on it for absolutely no reason, so now other init systems CAN'T compete on their merits. All because Red Hat is bound and determined to become the de facto owners of Linux.
Modernized, standardized boot scripts are a perfectly reasonable idea. systemd is not.
- Joined
- Mar 4, 2019
If systemd were just a replacement init, you'd be right. It's not just a replacement init. A replacement init would stop and start system services and do nothing else.
There were multiple projects to develop new inits. They were coming along nicely, until poettering decided he had to control everything in userspace and used his position at red hat as leverage to shut them out.
Systemd currently incorporates device management, DNS, dhcp, cron, hostname provision, network management, system logging, interprocess communication, ntp, user session management, container management, user home directory provision, and will shortly absorb the management of the entire boot process. All of its components are intermingled and non-trivially linked, requiring shims and compatibility layers when they aren't present, and it has infiltrated itself into so many aspects of userspace that it is a required dependency of more than one window manager. Gnome requires it. It is an enormous, bloated, hog of a system that brings none of the benefits it claims, whilst also creating a whole host of new, system-wide attack surfaces.
As for pulse: it's a bug-ridden, overly-complicated wrapper around ALSA, which poettering created entirely because he couldn't figure out how to multiplex audio to dynamic soundcards, and couldn't be arsed to ask.
Last edited:
- Joined
- Dec 12, 2022
Truly, truly, systemd saved my life! I love the systemd ecosystem! systemd-networkd! resolved! nspawn! Understandable unit dependencies! Capability management! Scope management! I don't need no docker, I don't need no LXC, all I need is systemd! I'd kiss Poettering on the mouth. It really was the cleanest, simplest solution for my problems as an end-user. Systemd must simply expand its scope to the ends of the earth because nobody else is providing better solutions, you silly whiners. Every time I've had a problem using something else because I wanted to avoid too much systemd, it ended up that systemd had the better solution. Too bad!
I used to use VMs since I hated docker and lxc so much, but nspawn is truly an unbelievable gift. I love containers now. The only thing I haven't moved into nspawn containers is my torrent client, but it's due to sloth, not the inability to run it with nspawn.
Also, I use Arch, btw.
I used to use VMs since I hated docker and lxc so much, but nspawn is truly an unbelievable gift. I love containers now. The only thing I haven't moved into nspawn containers is my torrent client, but it's due to sloth, not the inability to run it with nspawn.
Also, I use Arch, btw.
- Joined
- Oct 6, 2016
Be fair, the "stable ABI" of linux is just spinning up a wine instance.
That and it's still got 3.1 era DLL hell.
I thought everyone was whistling and shuffling away from that ever since pipewire dropped?
- Joined
- Dec 20, 2019
- Joined
- Aug 28, 2015
None of these burn me up as much as DNS.
I was blissfully unaware until I was digging for a problem and I went 'okay where's it getting this from?' From 127.0.0.53. What the fuck?
- Joined
- Aug 7, 2021
Yamaha CEO Pleased With Current Production Of Jet Skis, Alto Saxophones, Snowmobiles, Power Generators, Scooters, Golf Carts
HAMAMATSU, JAPAN—Despite concerns over the recent global recession, Yamaha Corporation president Mitsuru Umemura announced last week that he was content with the current level of production of Jet Skis, alto saxophones, snowmobiles, power generators, scooters, and golf carts. "Initially we...
www.theonion.com
- Joined
- Dec 13, 2022
Found this beauty while looking for a racist stable diffusion model.
https://github.com/AUTOMATIC1111/stable-diffusion-webui/discussions/6361 archive
Typical trannies finding offense with anything black related with the letter "n". Being offended on behalf of others per usual.
Got some good news though. Reddit is on the case and they've already had a discussion.
At least we get some reasonable people that realize the letter n just needs to be removed from the latin alphabet.
https://github.com/AUTOMATIC1111/stable-diffusion-webui/discussions/6361 archive
Typical trannies finding offense with anything black related with the letter "n". Being offended on behalf of others per usual.
Got some good news though. Reddit is on the case and they've already had a discussion.
At least we get some reasonable people that realize the letter n just needs to be removed from the latin alphabet.
- Joined
- Nov 21, 2020
Systemd takes stuff that worked for 20+ years and breaks it.
In the olden times, you put an entry in /etc/fstab and it was mounted on boot. Not anymore, if it's in a bad mood only half my NFS mounts get mounted. Logging in and doing "mount -a" mounts the rest with no errors. Supposedly if I fix a bunch of settings it will work.
Shutdown, a system used to kill all the processes and power off/reboot. Now it sits there going "Waiting to stop user uid=1000 unit" or some shit about half the time.
NTP, I have NTP servers in dhcp, they're ignored of course and it tries to use timesyncd and goes to various NTP servers on the internet. I finally told my DNS to just respond to *.pool.ntp.org with my local NTP server(s).
Of course then it decides it also doesn't like my local DNS and tries to go straight out to the internet instead of my local caching/adblock and local entry resolver.
Can I fix all this with Salt or Puppet or Ansible... sure, but it shouldn't be fucking broken to begin with.
In the olden times, you put an entry in /etc/fstab and it was mounted on boot. Not anymore, if it's in a bad mood only half my NFS mounts get mounted. Logging in and doing "mount -a" mounts the rest with no errors. Supposedly if I fix a bunch of settings it will work.
Shutdown, a system used to kill all the processes and power off/reboot. Now it sits there going "Waiting to stop user uid=1000 unit" or some shit about half the time.
NTP, I have NTP servers in dhcp, they're ignored of course and it tries to use timesyncd and goes to various NTP servers on the internet. I finally told my DNS to just respond to *.pool.ntp.org with my local NTP server(s).
Of course then it decides it also doesn't like my local DNS and tries to go straight out to the internet instead of my local caching/adblock and local entry resolver.
Can I fix all this with Salt or Puppet or Ansible... sure, but it shouldn't be fucking broken to begin with.
- Joined
- Aug 28, 2015
So they're asking for...
Total N Death?
By the way, did you find anything? I'm curious what people are up to.
- Joined
- Dec 13, 2022
Looks like the maintainer has no desire to deal with the tranny. Wasn't very well received by the community and only saw one or two supporting posts to 20 non-supporting posts.
Also looks like they tried a github merge with "fixing" the issue. It was close and not merged. https://github.com/AUTOMATIC1111/stable-diffusion-webui/pull/6368
Couldn't find anything on their profile that was interesting. The user either didn't post on reddit or has a different username over there so not doing much digging on it. I'll assume it's an assmad tranny unless shown otherwise.
- Joined
- Aug 28, 2015
That's excellent! But I originally meant your search for Moon Man-Positive models.
- Joined
- Aug 17, 2018
No, you had inits that could do all that before systemd. Like upstart which was already widely in use.
And even with the old init scripts, you can run services in parallel.
And with sane distros like Slackware, the inits scripts are quite simple - not that most users would ever need to touch them.
- Joined
- Dec 28, 2014
Am I the only one who thinks System V init files actually just made sense and were clearly separated into runlevels so that you knew exactly what they did and why? I have absolutely no clue what systemd is even doing.
- Joined
- Mar 3, 2021
Except he was always blaming other people's code for PulseAudio's fuckups. When "everyone else's code sucks" but even the most mild criticism of your shitty sound system can be deflected with "other people's drivers aren't coded properly! REEEEEEE!", it isn't long before everybody starts to suspect that you're actually just a delusional clown on a Red Hat-subsidized power trip. Poettering has earned his hatred.
- Joined
- Dec 28, 2014
If PulseAudio is so great then why does ALSA (widely regarded as a mess) work fine with a little tweaking?