Well I did all my deliveries on my 1954 Raleigh Suberbe. Then Took a nice tour on my French hand made 1978 super touring Motobecane. Relaxed sat back updated Slackware. Wrote this.
Everything seems to work just fine for me. I look out the window at my Buick and my F150 4WD and wonder. How many ways to get from point "A" to point "B".

Wonder what kind of a tool breaks other tools. If you use a pry bar to fix it may take hammer later.

Do not forget the handy mans tool duct Tape. You ever wonder why it is called duct tape. And what it was designed to do. Trust me I do and you can sweat it out of me.

come to think of it the vehicle I had the least trouble with was my 1953 Willys CJ3b. Has the starter really changed much since then?

Just like Slackware start me I will never stop.

It is time to let the Systemd team know. Put the pry bar down put the hammer away. You don't need duct tape. Build a init put it in /etc. and do it with pride,
not arrogance. Your not special anyone can count to 01.

As for Linus well sounds like a mechanic that scraped his knuckles.

Why not just stop reading/replying and just participate in other threads...?

4 members found this post helpful.

Because:

1. I believe that this sub-forum's main purpose is to provide help and useful information about Slackware. Having it polluted by threads like this one makes things harder for people eager to find occasions to help and learn. At least that's how I feel.
2. I'm afraid that this kind of thread doesn't make us Slackers appear like smart and nice people to newcomers.

4 members found this post helpful.

Because there are others who still post into this thread, including moderators.

Perhaps. This is an interesting technical discussion. If rules are violated we have moderators that can refocus the conversation.

2 members found this post helpful.

That's both off-topic and irrelevant.

Sometimes the temperature can get a bit elevated in a forum thread, as it has in this very thread, and that's understandable; people can get a bit fired up when the topic of a discussion is one they care about. However, that's no excuse for derailing a thread by posting off-topic material or making personal attacks. Nor is it helpful or constructive to ignore logical arguments posted by others and keep arguing against strawmen.

As you know, I posted a very simple analogy. It involved a car, a subject with which I'm intimately familiar on a technical level, but that doesn't actually matter one iota, as the analogy requires no technical expertise whatsoever. I can find nothing wrong with it from any perspective. and apparently neither can you, as you've yet to present an argument.

Shall we just leave it at that?

1 members found this post helpful.

What was the original thread?

Regards.

That's fine and you're entitled to your opinion. I disagree however that users will have difficulty in telling the difference between "noise" threads and "signal" threads and that this type of thread is "pollution" of any kind. Slackers, including new Slackers, on the whole are a well informed bunch who can easily differentiate and don't need any kind of guidance or baby sitting. This kind of thread only becomes a problem if users allow it to be one. Everyone who posted in this thread whether neutrally, positively or negatively helped make the thread - so 'invading' the thread with pleas to the staff or comments on the quality of the thread seem pointless and are still adding to the thread. I just don't get the "I've arrived in this thread to inform you all that this thread is a waste of 1s and 0s and should be closed/moved" mentality.

From my perspective - and I'm not including myself in this - Slackers on this forum have always come across as "smart and nice" people. I see people getting helped here - and getting a very high standard of help. I also see a lot of productive discussion and good technical threads rather than the tons of worthless chat/rants/raves you see at some other message boards. So no I really don't see how the odd silly systemd or similar thread is somehow dragging the place down.

The systemd debate will materialise here again and again. However annoying that may be, complaining and asking for threads to be moved/closed will not really achieve anything.

6 members found this post helpful.

So this is the new systemd discussion sub-forum now? The whole topic isn't related to Slackware in any way. Last time I looked Kay Sievers was employed by Red Hat. He had some dispute with our chief kernel maintainer. So lets be constructive: How is Slackware going to fix that?

2 members found this post helpful.

I see. So anything which isn't currently in Slackware and not directly related to Slackware cannot be discussed here according to you?

Kay Sievers is also the man behind udev, which is in Slackware. Red Hat contribute to the kernel, which is also in Slackware. So no I don't see your point. I also don't see what Kay Sievers being employed by Red Hat has got to do with why systemd can't be discussed here.

PV and the LQ staff don't seem to agree with you as they've let this thread go and don't seem to object to it (9 pages on).

gnome is also not in Slackware, is gnome discussion also banned here?

3 members found this post helpful.

I really don't think that until now anyone cared in which sub-forum this is.. Really now, moved or left alone, what's the difference?

I'm sure Tobi will read your posts and think about it (it's his responsability, isn't it) and that's that.. But for the members that read or write here, I fail to see any difference..

2 members found this post helpful.

I don't want to sound bias here but I rather see any Linux discussion here

If an issue affects only Slackware, it belongs here in the Slackware forum. If it affects all distros, it belongs in the linux-general forum.

OK. Serious Slackware Linux Discussion - There is some evidence that "Lenny and the Boys" are not content with just building an alternative init system. nor confining themselves to positive attractions (read "underhanded 5th column stuff" if you like) but instead are determined to achieve some kind of Grand Unification, a Core OS. Since they have been successful at pushing and/or pulling all of the major distros in, and since there now exists an actual CoreOS, with heavy reliance on systemd, cgroups, and containers they seem to be getting their way.

So we have to ask ourselves, I think, if at some point in the not too distant future, only Slackware, BSD, and possibly Gentoo, are left NOT using these "contributions", can we (Slackware users) be marginalized to the point of evaporation? Also, is it possible to get some element of the kernel code to favor systemd, and over time, completely eschew SysV?

OT Personal Bullshit - @k3lt01 - Did I mention that bridges over channels sometimes attract trolls?

That's what it sounds like from this quote by LP:
A complete makeover/takeover of Linux. A Borg-style assimilation.

2 members found this post helpful.