volkerdi |
02-20-2013 11:32 PM |
Quote:
Originally Posted by deadbeat
(Post 4896396)
...what is the problem with systemd? You can't even compare it to the mess sysvinit is.
|
Funny, my take is the exact opposite of yours.
Quote:
Systemd is well thought, robust and solves actual problems.
|
Like what? Try a search for "systemd crashing" and tell me again about how robust it is. I've been using Linux almost forever, and init has never crashed.
Quote:
Yes it doesn't work on anything but Linux, but last i checked Slackware didn't either.
|
That's an odd argument. As far as I know, adding systemd wouldn't help Slackware work on a non-Linux OS.
Anyway, we use plenty of things that are closely tied to the kernel and don't work on non-Linux operating systems, so that is not the rationale here. It's more like, if we're going to be dropping core functionality with years of careful evolution, it had better be a clear improvement. It doesn't take very much time on Google to see that not everyone is happy with systemd. And I'd guess that the usual Slackware user would be even less happy with it than the usual user of (insert other distro here). The benchmarks I've seen don't show an improvement in boot time (the opposite, actually), and users and developers alike have complained that it lacks the flexibility of shell scripts, that it is harder to create a systemd unit than to modify a shell script, and that it can easily lead to race conditions as processes start. It is far from simple, and it tries to do too much. It actually has to create sockets for services that haven't started yet in order to paper over the issues with things that haven't started up yet. And sysvinit as implemented in Slackware is a mess? Spare me.
Quote:
Have you (not just Pat but Slackware people in general) tried recent versions of it?
|
I have. Didn't care for it, and wouldn't want to have to support it. If you like it, there are a whole lot of distributions that use it, and I realize that we can't be everything to everybody. As long it is remains optional, I plan to avoid it. Unfortunately, the folks in charge of it seem to force it upon us, and everyone else. A healthy open source ecosystem respects diversity, and doesn't try to railroad everyone into being exactly the same. Without choices, you cannot choose a solution that fits your needs. That's not what we want, is it?
|