sure, because Redhat makes its most money with it's desktop edition

hm, no, I think the responsible persons from Slackware have obviously a better understanding about facts than you and that's why I trust them more.

redhat has realized that server ppl usually put whatever they use on the desktop
and i don't see what systemd brings to the servers at all (except useless info in logs and silent errors, looking at the bug reports)
so that lessens the reasons to correct the OP, a bit

anyway
exodus !

I'll hang on to Slackware and keep its old init. However, FreeBSD 10.0 and 10.1-RC have really caught my eye as an easy-to-administer casual desktop machine. [Open Office won't save spreadsheets on any of my PCs, though, so I have to use LibreOffice there.] Currently, I have no interest in knowing how other Linux distributions do things, whereas normally I'm at least a little bit curious. It's either Slackware Linux or no Linux for me, and I'll be glad to have my modern Linux knowledge base and skills fade into obsolescence as a result. So no, it's not an exodus for me, but absolutely there is a momentum shift. It's not just systemd by any means, but systemd does threaten to be the straw that breaks the camel's back. systemd is the one that affects my actual job and is not just another bloated, slow, myopic, ego-self-stroking FLOSS-related side project that I can simply avoid.

Should your hardware be supported, FreeBSD 10.0 is worth a look.

There is an interesting write-up about systemd here: Why systemd? (The author states he is not a fan of systemd, mainly due to it being huge.)

Also, there is this: http://uselessd.darknedgy.net/ProSystemdAntiSystemd/. A relevant quote:

My experience with the BSDs tells me that while I prefer its userland to GNU, the kernel is not as modern and robust as Linux. I use NetBSD myself, but my hardware only correctly works with Linux, especially X and ACPI. A few days ago, I configured a USB printer on OpenBSD and got a kernel panic. I don't remember when I had that happen on Linux to me the last time. So when Slackware switches to BSD (similar in spirit to the ArchBSD project, I guess), I'll switch to Void Linux or CRUX.

though I do not like the politics surrounding systemd, I am more interested of what I can do with my operating system after it has booted. So, I guess I will just trust Pat on the init system choice.

I don't have the horsepower for Gnome 3. Besides. I was just pointing out Puppy does not use systemd either.
I think Black Lab would though, No?

It seems to me that one of the main selling points of systemd is to facilitate virtual servers. Instead of each virtual host running an entire kernel+userland, you can run one kernel with each virtual host running its own systemd+userland.

In this case, I'll be on Slackware anyway. But yes, I'm not sure that systemd is good way.

Exactly what solarfields said
 

Man, I wish I had the gift of being this succinct.

sed -i 's/my thoughts/Exactly what solarfields said/'

For me, I'm with Slackware so long as Slackware is rock-solid, boots every time, and doesn't break if someone so much as farts upwind of the patch server. I'm less concerned about how it boots than that it boots every time. For me, what's running on it is more important than how.

The adoption of pulseaudio with no chance of other options would be a deal-breaker for me. Granted, it goes against the Slackware philosophy to not at least let the user install something else. (Even now, you *can* install systemd, if you so choose.) So I'm not too worried, even if it should start using pulseaudio. There would likely be a workaround and/or new packages for jack or something. :)

I trust Patrick to make the best decisions for slackware. I've used distros that use systemd and have had no problems with it. Actually I'm indifferent to it honestly. I'm happy as long as my system boots up and has no issues (other than those self-caused).

I'm planning on sticking with Slackware for as long as it's feasible to do so. I'm also heavily experimenting with LFS and custom system building to avoid using systemd at any costs. I've used it, I hate it, I wish it gone, destroyed, and utterly forgotten in a perfect world. Sadly this world is imperfect.

I feel as long as Slackware enforces the usage of sanity and sane software without conforming to trends and fads, then we'll be safe possibly even for years to come. The only problem we face is Greg Kroah-Hartman's kdbus. If it is ever pushed into the Linux kernel, then unfortunately we'll be locked into whatever final version of udev or eudev still supports netlink, unless Patrick starts experimenting with mdev, hotplug2, etc. udev alternatives with uncertain lifespans. The only alternative would be to wait for kdbus to be reimplemented outside of systemd, or move to systemd, which honestly is not an option for me.

To be honest with you, I have no qualms about activating the bail-out rocket and flying to FreeBSD world. I've been using Free/PC-BSD for a year or so, and have learned a great deal regarding it. Yes, hardware support is forthcoming in slowness, but I would expect a huge surge in developments if FreeBSD suddenly was infused with users and developers, maybe even package builders, and distributions leaders as well. Maybe we may even see Slackware-BSD rise from the ashes of Slackware-Linux if Patrick were to hop on board also.

The arctic climate in the FreeBSD forums can be quite lethal to tropical species migrating from the warm gulfstreams of the Slackware forums on LQ. :)

I'm already used to them, plus we do have our own *BSD forum here as well.

There are mass exoduses happening all the time...

...it's called distro hopping.


Nothing new here :P Enjoy your new X for reasons Y.