Now that the dust has settled, did he intentionally ruin Linux or was it accidental?
Now that the dust has settled, did he intentionally ruin Linux or was it accidental?
Now that the dust has settled, did he intentionally ruin Linux or was it accidental?
He's still around and kicking, that flamboyant fag.
He's definitely ruined Linux, just like Miguel de Icaza ruined Linux before him.
Ever noticed how he and Miguel got a job at Linux' direct competitor after their work was done? It seems almost like a reward. Miguel "left" for Apple if you can't find the info btw.
At least you can use KDE or Openbox and avoid GNOME entirely
intentional the arrogant prick is laughing at us
Ruin? Linux is only usable because systemd and pulseaudio.
This is the exact problem wtih systemd and pulseaudio. They allowed abject mouthbreathing knuckle dragging cromagnon fucking retards like you into the community.
>t. never wrote an init script in his life
all those homosexuals' complaints about "le .sh scripts are too hard to le maintain" sound pretty silly in a world where you run it through ChatGPT and have it instantly updated and rewritten
Turns out we didn't need systemd in the first place. Now the worm is deep in every Linux
>retarded larping zoomer namedrops chatgpt to auto-win argument
typical day on LULZ
Other than the 3 dozen or so that I wrote and maintained from approximately 2003-2009, I guess. Turns out if you're not brain damaged it's not actually that difficult to write an init script, and it also turns out you don't need a PID1 that takes over every low-level function of your entire fucking OS to parallelize init. The weaknesses of sysvinit have been addressed in runit, s6, openrc and upstart without tacking a Windows registry onto Linux. Also, guess how I know you've never written a systemd service? Since you clearly don't know how to do any actual system administration and just rely on whatever ships with your OS, what fucking difference would it make to you? Ahh, but there's the rub: systemd isn't an init system. It's a babysitter for retards like you who we didn't want in our community, bringing me back to my initial point
>NOOOOOOOOO MY HECKING SIKRIT CLUB IS NOT SIKIT ANYMORE
Please, neck yourself.
Pulseaudio yes. It gave us the mixing facilities we needed.
systemd not so much so. The practicalities of systemd revolve around one and only one thing - SKILL ISSUE. Most people hired as sysops after 2008 have a pretty shit idea of how Bash works, so they couldn't do their job just as well as the people who got the same job in 2003, but left for greener pastures. So to make this skill issue go away, did people suddenly start learning Bash? No. Lennart made an init system with .ini file structure for service files, so that Wintoddlers would have a much lower threshold of entry into the IT for adults.
The beginning
>package maintainers were tired of editing .sh scripts that had no strong standard
>Redhat sent recruiters to Germany to scower every underground teaboy bar they could find, until they found the twinkiest and smoothest boi
>RH asked twink to use init as a vector to make Linux as unnecessarily complicated as SELinux, so that Redhat could sell more service contracts and the NSA could add more backdoors
>smooth underaged teaboy twink swallowed, then agreed
>package maintainers got wet over having to edit fewer files, so they forced votes on which init system to choose
The great vote
>in one corner was systemd. Its proponents' strongest argument, "it's just an init system, bro"
>in the other corners were init systems that actually really were just init systems, didn't use binary formats, and weren't helmed by an autsitic harem twink homosexual
>in the audience were a few users that were worried about the twink teaboy's previous clusterfuck of a project (pulseaudio) and systemd's bloat and tendril-like structure
>the argument "it's just an init system, bro" won
>a bunch of distro owners left in disgust
A stop job is running
>Over the years the German twink teaboy has ballooned the init system like an inflatable buttplug until it throbs against nearly every aspect of Linux, each time claiming that some obscure edgecase won't work perfectly in his mind if an entire POSIX-style subsystem isn't replaced with his personal sex toy
>systemd has replaced the system DNS resolver, time daemon, syslog, udev, mount, cron, and now home
>all criticism is dismissed as trolling or angry script-kiddies butthurt about "muh init system shouldn't be contacting Google's servers"
>people who complain are told "lol why u mad? it was never just an init system, bro"
>ctrl-c to stop a job is still marked as "WONTFIX, working as designed"
>up until 7/2/2022 it was a joke that the twink secretly works for MSFT. Now he literally does.
>smooth underaged teaboy twink swallowed, then agreed
Hot.
>Also, guess how I know you've never written a systemd service?
wrong
>systemd isn't an init system
even wronger
systemd is worth alone for its ability to handle dependies properly and start multiple services in parallel. what kind of moron thinks that running all the shell scripts in a folder is an adequate init system? it's like you retards only like linux because of how shit it is and will refuse any attempts at making it any more bearable.
Shut up homosexual. Linux was better before systemd, which brought:
>binary logs
>monolithic codebase
>feature creep
And a ton of other bullshit.
logs
Fair, but there are benefits to both approaches.
codebase
Retards say this like sysvinit wasn't the exact same pile of programs found on every distro with a few ad-hoc scripts tossed in.
creep
Just don't use the features you don't want. This is an intentional use case to prevent Poettering's kraut autism from getting out of control.
>systemd is worth alone for its ability to handle dependies properly and start multiple services in parallel
The parallelism is useless because most init scripts are one liners that fork to the background. Systemd boots perhaps 1 second faster as long as no services fail, otherwise it decides to seize the computer for 1:30 minutes waiting for an issue that requires user intervention to be magically fixed.
>My computer I reboot once a year has to start in 12.75 seconds instead of 24.44 seconds
>ruin
works on my machine
systemd discussion is kicking a dead horse at this point. OP just wants to rehash the same shit over and over because his way is dying.
I keep getting "a stop job is running". How do I fix it? Im a boomer, dont understand systemD
Poettering disabled CTRL-C because an unauthorized user could be sitting at your keyboard, and closed the bug as WONTFIX. So just sit and wait the 1m30s.
>I keep getting "a stop job is running". How do I fix it? Im a boomer, dont understand systemD
the best way to shut down your pc (post-systemd) is to press ctrl+alt+f5 and press the power button 7x.
his work on pulseaudio went down in history as the best audiophile technology and is being used on audiophile systems and support both dolby/dts audio remixing and playback which I don't think will be supported for pipewire natively anytime soon (unless you use pipewire-pulse).
actually I would prefer to be using pulseaudio than pipewire since the cpu utilization for pipewire is a lot higher. recently though loonix rawdogged the audio drivers so I get stuttering and constant choppiness on audio when using USB and also the ability to sync to the clock/samplerate of the audio is much more impossible to do now, someone must've rawdogged the kernel space since unified audio streams (for usb and native audio) keep appearing and it's also causing this fucking constantly choppy audio with usb for some reason. what the actual fuck happened? there was zero issue on linux audio back when lennart was still working on the stuff and pulse was the shit. now linux audio is just completely and utterly broken to the point I can't make IEM measurements since my USB audio refuse to work unless I have the "test tone window of pulseeffects" open w h a t t h e a c t u a l f u c k. this is a kernel space bug. fuck whatever whoever is shitting up the code for snd usb audio.
aaaand I also tried to migrate to pipewire, same problem. it's just stuttering and occasionally the pipewire will fuck up on its own and make a loud white noise which sounds like what happens when a usb audio was slightly disconnected abruptly. someone must have fucked up the usb sound kernel code and it's preventing me from making music. holy fuck. the absolute state of linux. might have to find a really old distro just so the usb audio works.
this an external "dac"? many such cases with linux (if you are using one).
you have some bizarre hardware, i switched from pulse to pw and my major issues just evaporated instantly. now i get even better audio playback than on windows
fuck poettering
> be everyone
> shits on pulseaudio
> "best audiophile technology"
you fucking what
it's a kernelspace bug.
back when pipewire wasn't mainstream pulse was stable as fuck but now even alsa refuses to cooperate properly.
I see this as intentional sabotage to force people to betatest RHEL's pipewire 0.3 but unluckily my usb dac doesn't work well with pipewire, whatever the fuck that simultaneous virtual output is doing is fucking with the snd usb audio kernel driver
idk man. linux audio has always been one kind of a clusterfuck in whatever form its presented to us. it "just werks" until it doesn't and reasons for why things fail at "just werking" are numerous.