yes, you're right, I wrote one for the other.

I thought James Bond protected us against Spectre.

1 members found this post helpful.

a typewriter does

Glad I am not the only ones with nvidia issues from time to time.

as I see the website finally updated NVIDA Vaseline givers repo and my automatic script that builds the NVIDIA stupid blob that uses json to read.h my script looks for any xorg changes.
and then uninstalls nvidia then does a slack update . the sed goes and looks at the latest up loads to the site. The changelog had nothing in xorg. the nvidia blob was set with out uploading to that version to nvidia. And Pat did not write a NVidia fail for current. Current is not testing. This is a serious slack.
if any one want to ;look at Nvida server upload log ask them. I already. as far as slackbuilds and Nvidia. Get with it.
Waits for the slackware trolls.

Looks like we already have the troll...

The whole idea of current is testing software to ensure it is stable enough with each other for a release. Just because you use 3rd-party software that can't keep up with OPEN development doesn't mean Pat should halt the progression of Slackware.

2 members found this post helpful.

dude get with it is about a change log now you want to p[lay stupid with LQ and me test me. or current slackware log.
the 384.111 went to latest and the fuiking script I wrote to keep many systems up works now. you see the big picture. you want to harass me like Rworkman that just spews sht. he does good stuff what is your work. HTTP ?\
What you fooking do not get is was more than Pat being lazy. it was my script that looked for 384.111 and was never there. because NVIDIA A holes posted b4 they updated the repo.
I am tired of this sht it is Simple to me Pat pushed a up date with out checking wtf the users use. Get with it. I pay for this Stuff. do you.
You think Pat Cares what I use not after this. changelog is the back bone of so wtf Pat.
read the changelog. If pat you reading this just put in slackbook screw nvidia
https://github.com/Drakeo/update-nvidia-mkinitrd

You really should work on your grammar. Your posts are hard to understand.

What's going to happen if I "test you"? And what's testing you? Calling you on your rants when you, a. don't make sense, and b. when you're complaining that -current is doing exactly what -current is supposed to do.

In all your rants on this, I'm still trying to figure out why Pat is "lazy". Is it because he pushed a new kernel without consulting you? Is it because he didn't put an entry in the changelog stating 3rd-party drivers might be broken? Should he shine a Drakeo light in the sky whenever something might break your precious workflow?

Since you asked me to toot my own horn, I am maintaining 37 SlackBuilds on SBo, the amdgpu-pro SlackBuild, and a few other things on my github. But I don't do this to for bragging rights (which even though I'm in the top 5% of SBo maintainers with number of packages, I am still drastically under what some of the major maintainers provide -- there's two that provide around 500 each). I use my computer. If I come across a program that isn't on SBo that I want to use, I create and submit a SlackBuild for it. Someone in the community asked for help with an amdgpu-pro SlackBuild, and I helped create one.

I would think it'd be obvious by now that Pat doesn't care if proprietary drivers get broke on -current -- but I guess if it was obvious, we wouldn't be having this conversation...

1 members found this post helpful.

@bassmadrigal really, why bother?

Honestly, I don't know... This comes to mind, but I don't know the underlying reason.

Dear Frenemy, you are brilliant as usual! Loved that XKCD.

BTW, many but really many confuse the -current with a stable rolling release. For example, I read (with surprise) that someone jumped in -current only because (s)he wanted an updated GIMP, nothing more. Of course, hilarity ensued when our BDFL messed with the huge kernel.

Maybe it is just an, let's say... unlucky naming of the development tree. That "current" word make many to think about "latest", but not about "testing"

2 members found this post helpful.

their loss if they can't RTFM

1 members found this post helpful.

LOL! us regular LQ slackers know why, carry on.

2 members found this post helpful.

That's odd. I'm running 14.2 Multilib with a custom built 4.14.12 kernel and installed the latest nVidia 390 beta driver. Everything works just fine and it did ask me if I wanted to install the 32 bit libraries. From where in the logs did you get the idea Multilib is no longer supported?

He talk about the next next driver. Go an iteration further, where the 32-bit support will be put down. For eternity.

starting from 390 Beta