This is quite confusing after reading Sievers' reply on Google+ (third comment on the post) [1] > my last kernel patch is more than a year old, my last non-trivial kernel patch 2 years old. i stopped working on the upstream kernel "long ago" for reasons i cannot stand the attitude of these guys, i decided to work with grown up or funny, or grown up and funny people instead and i enjoy it a lot more. not sure what thi…
Linus will not be merging any code from systemd developer
31–40 of 59 posts
Re: Linus will not be merging any code from systemd developer
#32Systemd is soon to be integrated as the default init daemon for Ubuntu, one of the most user-friendly Linux distributions available. It worries me that Sievers, and the systemd team aren't approaching testing with an almost paranoid attitude. Linux is finally getting a foothold in consumer desktops, it'd be a shame for people to go back to other operating systems purely because "it broke one day, something about syst…
I haven't used linux on a desktop in several years, but my experience was that "it broke many days, something about everything". Why should this one component be held on a pedestal as make-or-break for the whole OS? Is a broken init daemon worse than a broken xorg.conf from a desktop user's perspective?
For example, editing your xorg.conf is virtually a thing of the past these days. I haven't touched it in years and run a fancy triple monitor setup.
Re: Linus will not be merging any code from systemd developer
#33Systemd is soon to be integrated as the default init daemon for Ubuntu, one of the most user-friendly Linux distributions available. It worries me that Sievers, and the systemd team aren't approaching testing with an almost paranoid attitude. Linux is finally getting a foothold in consumer desktops, it'd be a shame for people to go back to other operating systems purely because "it broke one day, something about syst…
GNU/Linux support has improved a lot since my first installation in 1995, but it is still hit-and-miss on laptops.
Re: Linus will not be merging any code from systemd developer
#34Re: Linus will not be merging any code from systemd developer
#35Oh, the actual bugzilla thread is (if possible) even more depressing: https://bugs.freedesktop.org/show_bug.cgi?id=76935 I had actually started to warm to the idea of systemd, thinking that it couldn't end up the same clusterf*ck of mismatched reinventions that didn't really solve any problems that pulseaudio was. I guess it's time to move to Debian/kFreeBSD and ignore this crap.
Ubuntu probably won't because they're user-hostile, but I really hope Debian and the other major distros move away from systemd.
Re: Linus will not be merging any code from systemd developer
#36Systemd is soon to be integrated as the default init daemon for Ubuntu, one of the most user-friendly Linux distributions available. It worries me that Sievers, and the systemd team aren't approaching testing with an almost paranoid attitude. Linux is finally getting a foothold in consumer desktops, it'd be a shame for people to go back to other operating systems purely because "it broke one day, something about syst…
I haven't used linux on a desktop in several years, but my experience was that "it broke many days, something about everything". Why should this one component be held on a pedestal as make-or-break for the whole OS? Is a broken init daemon worse than a broken xorg.conf from a desktop user's perspective?
Re: Linus will not be merging any code from systemd developer
#37Although I've heard a lot of others disagree, I like the fact that Linus' posts are straight and to the point. No sugar-coating or euphemisms, just telling the hard reality like it is.
...Is a good way to turn otherwise-skilled people with some problematic but fixable habits into people who refuse to work with you ever again. Brutal honesty works with computers, but it's not always the best policy for keeping humans productive. Linus gets away with it because he's a celebrity, and moreover the right kind of celebrity. These comments would look very different if the public mockery was coming from, s…
The team itself might be a self-selecting group of people who can work with Linus. But, overall, I'd say that his brutal honesty works "well enough". It might not be a good way to run a corporate project, but for an OS kernel, the benevolent dictator model seems to work pretty well.
I wonder how the kernel groups at Apple and Microsoft work though... or how FreeBSD is organized... that'd be an interesting comparison.
Re: Linus will not be merging any code from systemd developer
#38Systemd is soon to be integrated as the default init daemon for Ubuntu, one of the most user-friendly Linux distributions available. It worries me that Sievers, and the systemd team aren't approaching testing with an almost paranoid attitude. Linux is finally getting a foothold in consumer desktops, it'd be a shame for people to go back to other operating systems purely because "it broke one day, something about syst…
I still use multiple OS across my laptops. GNU/Linux support has improved a lot since my first installation in 1995, but it is still hit-and-miss on laptops.
Re: Linus will not be merging any code from systemd developer
#39Although I've heard a lot of others disagree, I like the fact that Linus' posts are straight and to the point. No sugar-coating or euphemisms, just telling the hard reality like it is.
It's clear that that the kernel dev guys and Kay have a history. I wonder if Kay would have been more open to accepting change requests to systemd without Linus's bad behaviour. It bears thinking about...
Re: Linus will not be merging any code from systemd developer
#40Oh, the actual bugzilla thread is (if possible) even more depressing: https://bugs.freedesktop.org/show_bug.cgi?id=76935 I had actually started to warm to the idea of systemd, thinking that it couldn't end up the same clusterf*ck of mismatched reinventions that didn't really solve any problems that pulseaudio was. I guess it's time to move to Debian/kFreeBSD and ignore this crap.