systemd is a symptom, not the cause (Score: 5, Interesting) by Anonymous Coward on 2014-09-07 17:27 (#2S4H) It's a symptom of the sickness of the Linux kernel/system developers' philosophy. There has been no innovation in the Linux kernel for ages and Linux itself has never done anything new. Filesystems? Done much better in other Unices. Multiprocessing? Done to death since the 60s. Different task schedulers? Ditto. There is nothing new in Linux itself, it's just an effort to clone Unix.Being such an effort, it was completed a long time ago. All there is left to do is to change the interfaces (how many times iptables interface has changed?), change the internal structures, change change change, for no good reason. This is what happens when you mess with a working program just for the fun of it. You eventually break it so bad that you enter a road impossible to turn from. The sickness has permeated into the very core of the kernel: device management. We have had tons of the same stuff which performed equally badly over 20 years. We had kudzu, then HAL, then udev, and now systemd-udev. This "sake for the sake of change" sickness has a cause: people think that they could automate the complicated tasks of installing an operating system, installing services, modifying hardware etc. It's not gonna happen. It's the year 2014 and I'm still having troubles with my sound card. The fucking sound card! I'm not even mentioning that I'm using the third driver for my graphics card and that's not working properly either. In order to make that impossible dream come true, they are screwing around, changing interfaces. This causes the "change for the sake of change". Even if we can stop the systemd madness now, RedHat will find something else to "automate" and "make friendly to idiot sysadmins who can't read a fine manual". In another ten years we could be boycotting something else like "stop the networkd madness". I really think that the whole Linux thing should be abandoned. Stop giving away code for free and decepting managers saying that it's as good as the ones real engineers (with a focus in mind) designed. Solaris could hotswap CPUs, now it's gone. Tru64 could do massive multiprocessing even back in the 90s, now also gone. All gone into the toilet bowl of "we don't need to pay that much, a clusterfuck of PCs are just as good and here is an operating system for that". Even small attempts at creating a proper desktop system was killed by the free shit. I remember QNX, but there were others too. I'm not even talking about where we could be in mobile computing if this Linux-dumping didn't happen. Re: systemd is a symptom, not the cause (Score: 1) by email@example.com on 2014-09-07 17:32 (#2S4J) This post comes to you from opensuse 13.1, so I'm not a lost cause yet, but ... you've got a good point. I'd add: in all this spinning of change-for-change's-sake, a lot of useful stuff has fallen off the wheel.My best example is this weekend's point of frustration: I've got a trackball with two extra buttons. How to configure them? Google it and you'll quckly find out the answer is currently: there is no way. Oh wait, you can install btnx. No, that is now deprecated. Or you can install some other 3rd party daemon thing that comes with no documentation. C'mon, guys!The worst is, for an opensuse user, is there used to be a slick utility called sax2 that did phenomenal work configuring X11 for you back when it was X11. The move to x.org broke that and they never updated it. There /is/ something called sax3 now but it segfaults as soon as it starts.That means, despite all the eyecandy, the version of opensuse I used back in 2004 was more useful to me in practical purposes. I'd argue the move from KDE3 to KDE4 is the same story: yes, better in terms of flash and maybe in terms of potential, but KDE3 as a desktop basically gave me better options and got me working faster.C'mon people: 5 button mouse, make it work. Re: systemd is a symptom, not the cause (Score: 1) by firstname.lastname@example.org on 2014-09-07 19:05 (#2S4K) My razer deathadder, a 5 button mouse, is working just fine. :) Re: systemd is a symptom, not the cause (Score: 1) by email@example.com on 2014-09-08 09:27 (#2S4Z) I'm happy for you. But what OS are you using it on, and how did you configure it? I looked it up at their site and it doesn't mention any support for Linux, so i assume you're using it on Windows using their driver. Re: systemd is a symptom, not the cause (Score: 2, Informative) by firstname.lastname@example.org on 2014-09-08 13:43 (#2S5E) What would be the point of me telling you that if I were running Windows? Nah, I'm on archlinux. I did some research before buying the mouse just to make sure it was supported. I just downloaded some package on the archlinux user repository. Re: systemd is a symptom, not the cause (Score: 2, Insightful) by email@example.com on 2014-09-09 12:38 (#2S6S) As a fellow arch user, let's agree that arch users have the advantage on everybody else here with the AUR. I'm surprised no one in any of the other distros has figured out yet what a massive advantage the concept of the AUR is. Re: systemd is a symptom, not the cause (Score: 1) by firstname.lastname@example.org on 2014-09-09 16:18 (#2S7B) If this were meatspace this would now be an appropriate moment for a brofist or a high five. :pI have a suspicion that the other distros don't have AUR equivalents because they don't necessarily have as high standards for their users as arch does. Anyone could put anything they want in the package they upload to the AUR, and it's up to the user to verify the PKGBUILD and ensure that he can trust the source. Or even just read the comments. Such reliance on the user's good sense of analysis is not necesarily common outside of arch. I think other distros are content to give you a way to clumsily access user repositories while making sure that you know they in no way support this endeavour. They wouldn't want to integrate user repos the way arch does and then have to deal with clueless users screwing things up and blaming them for it.