Well i discovered a nice thread on the Debian Forum "Slackware rejects SystemD", where they are rooting for Slackware and cheering the decision to use eudev and not systemd. http://forums.debian.net/viewtopic.php?f=3&t=126148

Nice to see the love :-) thanks for sharing!

For years Debian was one of the sanest distributions, so it's not too surprising some Debian users keep Slackware in their orbits (as another of the sanest distributions).

Slackware also doesn't cater to the lowest common denominator and assumes you're an idiot.

No, Slackware assumes you know enough, but anything else can be learned the right way, or relearned regardless of skill level.

Slackware's so-called compiling nightmare is actually a dead argument. Slackware already ships with the majority of dependencies resolved, and toolkits like slapt-get/gslapt, sbotools, and sbopkg can resolve dependencies manually or automatically for 3rd party add-ins from Slackbuilds.org or Salix's repositories just fine.

It's probably worth nothing the thread was entitled "Slackware rejects SystemD" rather than "Slackware embraces eudev" ...

... or even "Slackware rejects vdev"

1 members found this post helpful.

I emailed Linux format about 2 months ago wondering why Slackware isnt shown much on the magazine. Got an email about 3 days ago saying there about to do a big spread on init and systemd with a large write up on slackware. keep a lookout

5 members found this post helpful.

Just goes to show how respected Slackware is as a distribution and community.

2 members found this post helpful.

I think everyone is rooting for Slackware on this.

1 members found this post helpful.

Maybe that's because some of we Debian Wheezy users* just won't accept the Jessie FUD displayed at the likes of https://www.debian.org/releases/whee...ian-installer/, namely:



AAMOF, am trying to figure out how to install Slackware 14.1 as a Virtualbox guest through a Wheezy Vbox 5.0x host .

*Still unsure how this whole anti-SystemD Devuan project will eventually end up ....

People seem to like public displays of common sense.

And, over the years, we Slackers have seen many of them.

It's also an argument that's ten years out of date: nearly everyone who ships a codebase big enough for that to be a concern uses pkg-config, which will tell you exactly what (and which version of it) you're missing before a single line of code is compiled.

1 members found this post helpful.

The title of the thread (and most of the other comments both there and here) show a fanboyish misunderstanding. The fact that slackware has moved to eudev, which is binary compatible with systemd's udev, that slackware's stock kernel is systemd compatible and that there are no name clashes between systemd and slackware's sysvinit unless you deliberately choose to make them (by replacing, say, init, reboot and halt, which is completely unnecessary), means that it is trivial to have a "dual boot" arrangement on slackware. You can choose what to boot as the init by passing it in to the kernel with the init kernel option. For pedagogical purposes I have done just that. I can't say that systemd particularly impresses me, but it works OK.

So choosing eudev could be a path to systemd. Most probably, though, it means absolutely nothing at all, either one way or the other.

1 members found this post helpful.

Nice! Thanks for sharing that. Slackware all the way.

Thank you for the morning laugh. Always a hoot when people resort to calling something like this post fanboyish.

Regarding your last comment, the primary reason (and some would point out the only reason) for using eudev would be to avoid systemd. That is the purpose for Gentoo offering it as their site states: "eudev is a fork of systemd's udev with the goal of obtaining better compatibility with existing software such as OpenRC, Upstart, older kernels, various toolchains, and anything else required by (but not well supported by) udev." It is not to become compatible with systemd.

Ref: https://wiki.gentoo.org/wiki/Eudev

4 members found this post helpful.

On fanboyishness, I think your have made my point for me; almost all these systemd postings in the end turn out that way. Better not to have started at all.

On the remainder, this is the logical fallacy of the thread referred to in your original post. Slackware happens to use eudev because it provides support for additional things such as hwdb (and libudev.so.1 compatibility), which were not available with udev-182. Whether you like it or not, it is compatible with systemd. As I said, it is pure speculation as to whether it means anything else, such as that systemd will or will not at any point in the future be supported by slackware.

Like I said, a hoot thank you again.

4 members found this post helpful.