of course you would make everything better. stupid Redhat that they did not have employed you.

and btw, the only thing I see emotional is that once again, the in-official official Slackware forum starts to look a bit strange.
what has this topic to do in the Slackware forum? why not in linux general, or redhat?

just that people like you can say how they make everything better? uninteresting, where is code from you available to see?
lets talk about this, and does it has to do anything with Slackware, at least develop on Slackware?
no?
every poops from the debian, or from some other anti systemd forum becomes a mirror here, explaining things via copy and past the messages from there.
Where is the relation to Slackware, are Slackware users so poor with their distribution that they have no other interesting topics? Talking about software they have not even installed, repeating things via copy and past they hardly understand them self?
I would vote for banning from this forum all such systemd threads that are not related to implementations details on Slackware like for some of the gnome implementations.
I think it would make this place a better place, and imho is linux general the right place for topics like that.

1 members found this post helpful.

I don't see how his statement wasn't the truth. He said this issue isn't our problem, which, right now, it isn't. It won't be our problem until/unless Pat decides to add systemd to Slackware, but at that point, this specific bug is likely to be long gone.

5 members found this post helpful.

"Lie" indicates that the person making the statement knew that they were stating something that was not the case.

That is different from being incorrect or wrong, which does not indicate that someone is dishonest.

A github commit today does not magically remove the broken instances already deployed in the field, so I don't think that you proved anything about the bug not existing at all.

This thread has become exactly what I did not want; another argue-fest with @a4z about systemd.

Systemd doesn't love you @a4z; just give it up. It will never call you.

1 members found this post helpful.

I think it would be a better place without your comments, but that isn't my decision to make. You have a pretty high rep, so I assume that you can be occasionally sane and helpful. Just not in systemd threads.

My intent in stating was to prevent this thread from becoming the standard bleep-storm that you always appear to create when systemd is mentioned.

1 members found this post helpful.

It's not a Slackware are problem because luckily, Slackware avoided the problem preemptively. It's about the fact of practices have not changed regarding how the developers attitudes and treatment of the project.

I wouldn't be surprised if eudev and elogind haven't found bugs from their extracted code that they themselves fixed.

2 members found this post helpful.

Well, its not a present Slackware problem is what I meant. Slackware doesn't need to run systemd for it to cause Slackware problems in the future with its dependencies.

Everything has bugs. I'm sure they have found some in those projects. The systemd developers are making an integrated system. Its their goal.

What do you think of fuchsia? https://github.com/fuchsia-mirror

Well, RedHat has certain goals with systemd.

Those goals may not adequately support non-enterprise environments. I'm not claiming that RedHat is sabotaging desktop environments or anything like that; RedHat's money is in enterprise server pools and that's their focus.

Integration has pluses and minuses.

1 members found this post helpful.

Surprised it took them this long.

It'll be interesting to see the results of the project, if any.

It won't be the first time someone has made an alternate kernel...

2 members found this post helpful.

I saw this today in a re-tweet so I followed the link to that SystemD conference.

Here's the title of the talk.

Presentation: Talking to systemd from a Web Browser
https://cfp.systemd.io/en/systemdcon...blic/events/21

Fact: I do not start this stupid threads here that give Slackware users a chance to show the world how ignorant and technical unskilled they are.
Fact: you do comment those threads as much as I do, as several others do, but since they fit in your world view it is ok, right?
So address what you say to your self and some other prominent participants,
Fact: in contrast to several others, as you can read in the meanwhile year of history to this topic, at least I do not spread FUD, lies and technical bullshit.(Fact)
But I agree with you on one think, it is actual better to do take some break from this place, since it is obvious that some super Slackers like you have noting to say to technical stuff anyway and therefore are focused on spreading the sect like believes, mobbing everyone who does not agree..

and sorry when I misunderstood you 'not our problem' statement, I thought you address others with this statement and continue to repeat some lies about bug ignoring from some developers, as has been brought over and over in such threads as you can read in the history, also a fact.
But in contrast to others, I can learn when I understand or do something wrong.

Slackware, the place with users unable to boot into a different runlevel when they have to work with a different distribution not hesitate to shout this out into the world (just an other fact in context of systemd if you remember;-)
Ok , this was bad, but should show you why I would like such systemd or simmilar threads to dissipater out of the Slackwaerforum in to the Linux general section, where I btw never comment such threads, just an other fact.
But I guess, as for al sect members, all these facts are possible to many facts for you and will trigger just an other backfire effect.

1 members found this post helpful.

Maybe it's just me, but this doesn't really sound like a good idea.

2 members found this post helpful.

So systemd wants to duplicate a webmin-like interface? No thank you. That's like giving sshd complete access to the root system without a password stopgap.

4 members found this post helpful.

My thoughts exactly when I saw that!

That is, how shall I put it... INSANE!

But they are trying to build a single-application-as-an-operating-system, so I guess it will need a web server, email server (won't that be fun), editors, sensors and probably even a few games...

But as someone has already observed, it isn't our problem...

3 members found this post helpful.

systemd is much more than an init and much more monolithic, so it's just inevitable. It doesn't mean that someone can't just fork the project in question and effectively remove the dependency on systemd. There needs to be a real will to do that however.

3 members found this post helpful.

You have serious problems you should look into getting helped with. You calling the users of a distribution(s) as those in a "sect" should have been a sign even to yourself.

5 members found this post helpful.