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.
I know this is old and I've read countless threads... i read some of Poettering comments regarding systemd and it sounded condescending to say the least.
It is totally unstable and is trying to take over the role of other packages even before it can do the basic - boot up w/o crashing and to keep the system running w/o crashing for NO REASON!
I just find it real sad that such a decision has been made by Red Hat and forced down the throats of all other distros. Sounds like Animal Farm to me. Criticising M$ and then turning out to be just like them for the sake of profits?
I just hope they'll never release this 'kraken' for real
In DistroWatch Weekly, Issue 532, 4 November 2013 there is an article about this whether or not to take over in Debian as well:
Members of the Debian project, one of the Linux community's largest and longest-living distributions, had a lot to talk about this past week. The first topic of interest is the idea that Debian could benefit from having a new init system. To date Debian has used a more traditional init system to get the operating system from a cold start to a running environment and some people feel Debian would benefit from using a more modern init system such as Upstart or systemd. The suggestion kicked off a heated debate on the Debian mailing lists as people chimed in with their opinions for or against each option. As a result, Debian's tech committee as been asked to vote on the decision as to which direction (if any) Debian will take in the future. While the decision is unlikely to affect desktop users directly, it will impact system administrators and package maintainers who may soon face a new approach to managing services.
I know this is old and I've read countless threads... i read some of Poettering comments regarding systemd and it sounded condescending to say the least.
It is totally unstable and is trying to take over the role of other packages even before it can do the basic - boot up w/o crashing and to keep the system running w/o crashing for NO REASON!
I just find it real sad that such a decision has been made by Red Hat and forced down the throats of all other distros. Sounds like Animal Farm to me. Criticising M$ and then turning out to be just like them for the sake of profits?
I just hope they'll never release this 'kraken' for real
Sorry for the rant.
Eh,.. sorry man. RHEL 7 will have systemd, supposedly. I can't find anything on the redhat site itself, but the internet is full of explanations of how to deal with RHEL 7 and systemd.
Last edited by szboardstretcher; 11-04-2013 at 09:15 AM.
not going to start another heated debate whatsoever.
I think we all know that systemd does not have much to offer except for slightly faster boot up time.
Everything else is much more complicated in terms of configuration. I do not mind if it's well documented/coded. but try to look at some of the source code. It's really bad... hardly readable. And the only 'documentation' you get is from the 0pointer website. Information are all over the place... it just doesn't make any sense. At least not to me.
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Rep:
I am running systemd v208 for 4 weeks now, and before that 207 and 206.
Didn't had a single crash.
I am running this on slackware.
What I am seeing so far is that even tho it is immature, it does have lots of potential.
currently its still in beta phase imo.
it has passed the development phase.
there is a reason that RHEL 7 is not out yet.
Red Hat is going to use systemd in RHEL 7, so unless RHEL 7 is out, systemd is not 100% stable yet.
The biggest problem is that functionality that are now in other packages will be merged
- ConsoleKit (completly merged)
- Util-linux (some functions)
- udev (completed merged)
- and probably more
Instead of starting Yet Another systemd Thread, I recommend that you (and everyone else here...) actually take a step outside lq.org/questions/slackware-14 and do some research.
These posts are embarrassingly uninformed. You say that systemd isn't documented, or that you can only find crap documentation on 0pointer. What? systemd is a freedesktop project and is very heavily documented at http://www.freedesktop.org/wiki/Software/systemd/. These look like posts from early 2011.
I love Slackware as much as the next guy around here, but I've also grown to really like sysytemd because I actually tried it out (and had no problems - imagine that).
I have an installation of Arch which uses systemd and it's trouble free. There are lengthy explanations from the Arch devs on their forums which explain why they use it. They seem pretty sold on its benefits, just as there are people who are equally opposed to it here and elsewhere.
I'm not saying anything either way, just that both Slackware and Arch work very well for me.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.