Website tells users to switch to Slackware in protest of systemd
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So ntpd and time aren't affected, but it's not FUD on any level that hearing news anything has been "added" to systemd, never has a positive ring to it.
Something new added to the Linux kernel always welcomed. Something added to Xfce, again good news. Something added to ZFS regardless of OS, again good.
...but systemd... Somehow always generates a groan and moan.
Tobi is the only one actually being resonable re: systemd. The naysayers are comically ignorant and keep spewing the same FUD that was going around a year ago.
Unfortunately there's a lot of ignorance on both sides of the systemd debate. The 'naysayers' don't have a monopoly on that one.
In this case Tobi is right, leaving aside any implementation quality issues, systemd's inclusion of a smtp client makes sense given their stated project goals, and has absolutely no impact on the rest of us at all.
Now, if you were discussing embedded systems from, oh, the 1980's, then the size of the NTPD server would be a sticking point. (A whole megabyte when even a fully tricked out system might have only 64K.)
But now we are in the 21st century. ntpdate (not statically linked, so this size is too small) is ~95Kb. Any systemd embedded system will have some type of cron, won't it? So just run ntpdate on a cron job and be done with it versus creating a new specialized client.
Somehow I'm not surprised that systemd contains its very own logger. How special.
systemd aims to be a suite of services that make it easy to set up a system from scratch without having to rely on daemons from outside the suite.
Somewhat the same thing like Busybox, but with a different focus. This is not at all about size.
The problem of dealing with FUD from the pro-systemd camp is they say everything but systemd is deprecated or will be deprecated. All this focus has limited choice to even attempted elimination of choice where-as the anti-systemd camp is saying that there are choices and all this deprecation is FUD and systemd isn't the only choice.
The problem of dealing with FUD from the pro-systemd camp is they say everything but systemd is deprecated or will be deprecated. All this focus has limited choice to even attempted elimination of choice where-as the anti-systemd camp is saying that there are choices and all this deprecation is FUD and systemd isn't the only choice.
That is not at all true. Please provide examples. YOU said:
Quote:
So... that means both ntpd and time just got deprecated... at least they're now wholly focused on trying to deprecate the entire GNU operating system outright rather than just bits and pieces of GNU/Linux.
First of all, ntpd is not being implemented in systemd. "just got deprecated" - how is this not FUD? And time? Deprecated? Do you know what deprecated means? Do you know that ifconfig is actually deprecated?
And the entirety of GNU? Come on, Reaper, you don't really think this, do you? Do you have proof that they want to do this? Or is it just FUD?
Last edited by fatalfrrog; 05-31-2014 at 11:40 AM.
First of read where I recanted my statement before you mouth off...
Then go read the websites all surrounding systemd's promotions. Unless you're 100% clueless and can't use Google, I doubt I need to say otherwise, especially where the comparison of ConsoleKit versus systemd-logind or any other part of systemd.
First of read where I recanted my statement before you mouth off...
Then go read the websites all surrounding systemd's promotions. Unless you're 100% clueless and can't use Google, I doubt I need to say otherwise, especially where the comparison of ConsoleKit versus systemd-logind or any other part of systemd.
Since you find the situation easy to follow, perhaps you could tell me if the following is correct:
Lennart Poettering and Jon McCann decide they no longer wish to maintain ConsoleKit.
Rather than inviting others to adopt the project, they pass maintenance of the code to Martin Pitt (of Canonical) on the condition that he rename the project. They then declare the ConsoleKit project "dead".
They don't post their decision on the project's mailing list or otherwise contact those who've been relying upon the project. An announcement of the project being dead was eventually made (but not by the maintainers) on the Gnome mailing list, and apparently Fedora devs were notified as a notice of its demise appears in their Wiki.
No renamed fork of the project is ever announced by Canonical. The project is eventually dropped from Ubuntu, again with no invitation for others to take over maintainership.
And thusly ConsoleKit joins HAL and others in the giant coffin that is still being filled with projects.
These Red Hat pieces disguised as "open source projects" didn't even reach 1.0.0 and with udev they abandoned version numbers altogether and switched to build numbers. I think, the best idea is to ignore the whole Fedora-GNOME-freedesktop-CoreOS pile as the BSDs do.
Well HAL is salvageable and with some patches still builds correctly. In all, HAL could be effectively revived better than other projects because HALs functionality was only replaced by ConsoleKit and other projects. If BSDs can still use HAL, why can't we?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.