Something definitely wrong with this article..... (Score: 2, Funny) by email@example.com on 2015-05-02 16:28 (#88ZM) ....not a single mention of systemd. ;-) Re: Something definitely wrong with this article..... (Score: 1) by firstname.lastname@example.org on 2015-05-02 21:09 (#891A) You can get your fix if you check out the distro's web page, which states Technically ConnochaetOS follows the KISS principle (which means no systemd, for example). It is build on top of the GNU/linux distributions Slackware and Salix OS.I'm curious, but leery. Slackware takes some learning, and this appears to be a one-person distro, which is hard to pull off effectively. I'm willing to give it a try though - I agree we need a replacement for init, but definitely am adverse to systemd (and the team pushing it).So, how the hell do you pronounce this moustachioed distribution? Re: Something definitely wrong with this article..... (Score: 1, Interesting) by Anonymous Coward on 2015-05-03 04:22 (#892R) As long as they keep it simple, Slackware is remarkably easy to modify and customize. ConnochaetOS appears to be using the FreeSlack listing to blacklist the non-Free software that ships in Slackware. I have not tried it out yet and so I do not know if there are any other changes at this point, but FreeSlack was straightforward to setup. This should be maintainable by just a few people.The maintainer did state on their forum that the primary reason for resuming is because of systemd frustration. Slackware, through Pat, has stated that they will hold out until it is no longer feasible; probably until KDE adds it as a dependency.As for pronunciation, how's your Greek? Re: Something definitely wrong with this article..... (Score: 1) by email@example.com on 2015-05-03 18:55 (#8A7V) Slackware, through Pat, has stated that they will hold out until it is no longer feasibleDo you have a link for this? Re: Something definitely wrong with this article..... (Score: 2, Informative) by firstname.lastname@example.org on 2015-05-03 19:32 (#8A9M) I can't find anything exact, but these seem to be useful:http://www.linuxquestions.org/questions/slackware-14/the-mass-exodus-if-slackware-uses-systemd-4175523380/http://www.linuxuser.co.uk/features/systemd-for-better-or-worse Re: Something definitely wrong with this article..... (Score: 3, Interesting) by email@example.com on 2015-05-03 19:35 (#8A9N) Got it. Here's a quote from about halfway down this interview: http://www.linuxquestions.org/questions/interviews-28/interview-with-patrick-volkerding-of-slackware-949029/LQ) Right now, there are a number of potentially intrusive technical changes coming to some of the major distributions. How do you feel some of these will impact Linux in general and Slackware specifically? Are there any you would considering merging into Slackware? (55020 & tuxrules)volkerdi) Yeah, I see a few things coming down the line that may cause a shakeup to our usual way of doing things, and could force Slackware to become, well, perhaps less UNIX-like. I guess the two big ones that are on the horizon are Wayland and systemd. Whether we end up using them or not remains to be seen. It's quite possible that we won't end up having a choice in the matter depending on how development that's out of our hands goes. It's hard to say whether moving to these technologies would be a good thing for Slackware overall. Concerning systemd, I do like the idea of a faster boot time (obviously), but I also like controlling the startup of the system with shell scripts that are readable, and I'm guessing that's what most Slackware users prefer too. I don't spend all day rebooting my machine, and having looked at systemd config files it seems to me a very foreign way of controlling a system to me, and attempting to control services, sockets, devices, mounts, etc., all within one daemon flies in the face of the UNIX concept of doing one thing and doing it well. To the typical end user, if this results in a faster boot then mission accomplished. With udev being phased out in favor of systemd performing those tasks we'll have to make the decision at some point between whether we want to try to maintain udev ourselves, have systemd replace just udev's functions, or if we want the whole kit and caboodle. Wayland, by comparison, seems fairly innocuous, assuming that they'll be able to implement network transparency either directly or through some kind of add-on compatibility layer. Again, another thing that most desktop users don't have a lot of use for but many users can't do without. I like X11, and would probably stick with it if moving to Wayland meant losing that feature, even if Wayland's rendering method carried with it some benefits like reduced rendering artifacts or increased video performance. I guess we'll just have to see what the overall benefit is when it's far enough along to make such comparisons. Re: Something definitely wrong with this article..... (Score: 1) by firstname.lastname@example.org on 2015-05-03 20:19 (#8ABH) Thank you!