You are hitting the nail right on the head here. This thread is no fun at all. And I am ashamed of some of the remarks I read.

He's not suggesting that is the security model at all. *You* are. He's asking if *you* have evidence that the maintainers are leaving you exposed on purpose.

Yes. I have done in the past, I do now, and will continue to do so in the future. I'm not getting my knickers in a twist just because of some longer than usual delay in updates. Eric implied there's something big coming, Pat said he's OK. That's enough for me. I don't need them to tell me all the details of what they're up to.

Agreed.

Yeah, I'm unsubscribing from this thread, it seems that it has taken a turn for the worse.

I think people just don't understand how Slackware is ran by its staff.

Slackware, even in -Current, has never been a rolling release, bleeding edge distribution. Even -Current is tested for stability. We will never have access to Patrick's private Slackware-Bleeding-Edge repository, and the informality of Slackware will continue.

Eric and Robby both have repositories so use them if needed.

If you want true Bleeding edge, get Funtoo and use Experimental.

Pat said he was OK. Can we mark this thread as solved and close it up? Eric is right, this thread is just no good anymore.

In my opinion, Slackware is the best computing platform around, even if it never sees another update.

Member response
 

Hi,

So you were referring to the USMC, I was in the Air Force and we would never question our leadership nor demand a explanation. The AP's would have marched us to the brig and rightfully so. We are not in PV's army but users of his distribution. You making demands will not get you anywhere, here at LQ or with Slackware's PV.

By your ideals! PV has been working the same over the years on Slackware. Aligning someone by stringent Military rules and how things should be conducted falls short and by someone who has no basic common sense nor ideals how the organization is controlled by the maintainer who sets the environment. I have seen this many times over the years with someone attempting to dictate how PV should control this Gnu/Linux.

cwizardone, you are not the first and probably not the last that recommends that a feedback path should be made available to the users. But that is not PV's way of doing things. Right or wrong still his way not yours to dictate! As to the misunderstanding between us for the 'The Basic School' statement, I did take it personally since I would never think someone would suggest that USMC way of doing things is right. I was an Airman and would never align in the way you have stated. I would not question my commander nor anyone above my rank unless it was life threatening. Then I would follow the 'Military code of conduct' but not challenge but question by doing so graciously and with respect/honor.

I have spent more time on this topic than intended and will cease now. Going no where!
Sad that some people have issues with something that they cannot control nor change. Just spinning our wheels and going no where.
At least we should move on and let this die.

But, but, but.... this ISN'T the military.
Can't change it? True. Has this happened before? Yes.
Will it happen again in the future? Most likely.
Regardless, this is not the way to run a business, and, yes, like it or not, that is what it is, a business.
There really nothing more to say.

On purpose? I don't know. Stopping to provide patches/inform about security problems on the security mailing list without any notice at all may be on purpose, it may be not, how would we know, there is no communication. But that doesn't change a thing. What is the point in a security mailing list when it stops being maintained without any notice?
As I said, I won't recommend Slackware anymore until this has changed and will stop using it for any purpose I would normally use it for from now on. I wouldn't tolerate this from any other distro and I don't see why I should for Slackware.

@ReaperX7: This is not about being bleeding edge, this is about security patches.

I got it the first time you announced this. I am happy to wait for the updates. I'm a Slacker. :)

This sounds a lot like this thread. I wasn't thrilled about it then, nor am I now, but I'm willing to ride it out until things start moving again (of which we have been assured will happen). The sky isn't falling, but at the same time the situation isn't great. I don't think anything further can (or needs to) be said about it...

You are still making a claim that security updates have stopped. What is the evidence? If it is not on purpose, then what else can it be, by accident?

I do not understand what is up with these type threads and the "going home" announcements.

Slackware meets my needs perfectly and I think there are 'hints' in the Current Changelog that points to amazing changes on the way. So I do recommend and will continue to recommend Slackware to people.

Also, mancha is nice enough to provide security info and instructions on how to apply the changes. So you can apply any patch you think you need, it is not really that difficult :)

John

This also goes back to having an in-house repository and maintaining it. You shouldn't have to rely solely on Patrick. You should learn to rely on yourself, your own skills, and your own packages and patches.

Stop blaming Slackware, Patrick, and everyone else for your lack of doing. It's getting old, tired, and dull to hear this droning on about Slackware and what it doesn't have.

Security is a two way street. It's part distribution, and part administrator. If you find a patch before Patrick, make a patched package, use it, and then contribute back without expecting it being rolled in. Why is it adamant Patrick has to be the sole source of packages? Why else do Linux distributions release source packs? It's for in-house administrators to build their own packages with their own patches.