Thanks you for that intelligent reference, but that does NOT make a response to the fact that Slackware 14.2 is basically incompatible with any Radeon proprietary driver, because it ship a X.org and Kernel version risen to madness...

Even if I will "fuck off", like you kindly suggested, the issue will remain, until this thread will be locked or abandoned.

STOP THE MADNESS! TAKE YOUR SLACKWARE BACK!

How is that become Slackware's fault?
Slackware choose to pick a LTS kernel, which is a great decision and as far as i know, there isn't any statement saying that it WILL work with any proprietary driver. I used a NVidia-based legacy GPU and everytime a new kernel comes, i had to rebuilt the kernel sorce to make sure NVidia proprietary works but that's my own problem, not Slackware's.

AMD is known to very slow on supporting newer kernel releases so it's nothing new.

if the amd people don't care if a new X version is out since 10 months (and new kernels are too) and that they are very slow in releasing new versions do the distribution maintainers should stop including new software?
this is the main reason why other distribution completely removed the ati proprietary drivers from their repositories.

why distribution maintainers should care or be considered responsible for the various ways upstream behaves, especially in case we are talking about proprietary software?

it happened already in Slackware a lot of times in the past and that's why, personally, if I want something usable with 3d, I buy nvidia hardware choosing between whatever doesn't use optimus...

(willy has been faster than me)

1 members found this post helpful.

Thanks for making me laughing hard! The Arch daemon taken over your soul, right?

So, Slackware have so much end-users that dismissing half of the major Video Cards is nothing?

Not that Slackware ship on extra a PHP7, able to make it usable on niche case of the web-developers, or being PAMified, then making it able to be used at least on a stupid Office environment...

I will ask you punctually, willysr... Who pay you to sabotage Slackware? Ubuntu? RedHat? Unknown Indonesian forces?

Be honest, you own some NVidia shares, right?

no, just had been left in the shit a lot of times by ati in the past.

1 members found this post helpful.

Clearly i'm working on projects to help Slackware users. Can't you differentiate between contribute and sabotage?

My question to you: Do you want to sabotage Slackware Linux community?

1 members found this post helpful.

All --

One thing to bear in mind is that the Subject of this Thread is Requests for -current (20151216)

Current is by nature unstable from time-to-time because otherwise, how will new stuff ever get into Slackware Stable ?

I trust the judgement of volkerdi and the Team to 'do the right thing' so arguments here about which way to steer -current is a lot of unnecessary noise.

And as volkerdi said on this Tread just after releasing 14.2, 'Keep them coming'

Anyhow, my $0.02 worth.

-- kjh

2 members found this post helpful.

And one more important thing to bear in mind is that the proposals made by that pack of bitches living there, in one day will end on your computer, as stable version. That's the problem!

It is not about a abstract current, but that that crap ended with myself being unable to use Slackware 14.2 on a fucking count of six computers, ranged from Pentium 4 to Buldozer x8. While I'm earn my food in the last ten freaking years from Slackware and derivatives.

So, dear kjhambrick, personally I do not need your valuable contributions, because I can't use them anyway, literally.

So, like 55020 said kindly somewhere, be nice to fuck off.

NO, but I arrived at conclusion that part of so called "important members of Slackware Community" try their best to make Slackware Linux unusable, pushing show-stoppers from severe hardware issues to lack of support for various wide supported APIs, ie. PAM.

I still believe it's not Slackware's fault. With so many hardware variant out there it's impossible to support all of them, mainly legacy hardware.

As i said, there isn't any statement about Slackware will support spesific or all hardware in the announcement.

Same goes for packages. If you can't find the packages you need, feel free to contribute, be it in SBo, github, or in your personal repository space.

2 members found this post helpful.

are we starting an argument again on PAM?

Why we should do? yet to note that our acclaimed Alien have no more than two months to demonstrate his skills on a full PAM-ified and SystemD-fied distribution like CentOS 7, if he want to hope to come back with some money to his wife and child. Sadly, but that's the truth.

Theoretical question: A basic/normal distribution, aka a PAM-fied Slackware, would be helped him to learn fast the required skills?

1 members found this post helpful.

IF you dare to call my two Bulldozer FX 8350 x8, every one with 32GB DDR3 1600MHz RAM and 6x1TB RAID5 (Western Digital Blacks, BTW), shipping also every one a 1GB Radeon HD6450, as "legacy hardware", permit me to say you kindly and with all respect: fuck you!

I'm not pointing at your hardware spesifically. I just saying that it's impossible to support all hardware variants out there, mainly legacy hardware. Once the kernel devs agreed to remove it, it's over unless some third party project is willing to support it longer.

Same goes for new hardware since not all hardware vendor contribute to the Linux kernel, that's a fact.

Again, i'm talking in general, not spesifically pointing at you.

2 members found this post helpful.