Hello tallship,

There is a 5.4.0 kernel in testing or extra. Maybe I should give
that a try.

heh. I get it, you like to cook with gasoline ;)

Not if I can help it, but I don't mind if I need too..

Since we last talked about this kernel 5.4.1 has been moved into place in current. I updated and unblacklisted amdgpu and all is happy now. We just got 5.4.2 and all is still well. I have all the regulars built and installed for xfce now. I have WiFi and the desktop is happy now.

So things are looking good on my laptop finally.. :)

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 27 Nov 2019, Al said the following...

I'll send you a Netmail about a good list.

I got your netmail, thanks. I'll look in on that.

Kewl, I hope that helps :) They're a good bunch of folks, no trolls, and no assholes like what you get on freenode or LQ.

Sid, you like living on the edge lolz.

At one time, I was pinning so much stuff I just moved to sid and found it quite comfortable. I wouldn't do that after a release though.. ;)

One thing people often don't grasp, is that, since Testing is almost stable,
or at least rolling towards the 'next stable', if there's an actual bug in a package, it's actually Sid that gets the fix first, so rolling back is something that one must be prepared for in testing.

This makes sense, because the dev version of something is getting all of the attention, and only after some quick elbow checking does it get pushed to testing.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)

I got your netmail, thanks. I'll look in on that.

Kewl, I hope that helps :) They're a good bunch of folks, no
trolls, and no assholes like what you get on freenode or LQ.

Shortly after I wrote that, kernel 5.4.1 was added to current. I did a
slackpkg update and upgrade-all, removed amdgpu from the blacklist and
all is well now. We've since got 5.4.2 and I have my desktop running with
all the usual bells & whisles now.

Life is good.. :)

One thing people often don't grasp, is that, since Testing is
almost stable, or at least rolling towards the 'next stable', if
there's an actual bug in a package, it's actually Sid that gets the
fix first, so rolling back is something that one must be prepared
for in testing.

Yep, things can break there but the fix is usually quite quick.

This makes sense, because the dev version of something is getting
all of the attention, and only after some quick elbow checking does
it get pushed to testing.

In the case of slackware-current it looks really good to me. I don't know exactly what Pat is shooting for so it may take a while yet, but it's all coming together nicely.

Ttyl :-),
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 06 Dec 2019, Al said the following...

There is a 5.4.0 kernel in testing or extra. Maybe I should give
that a try.

Since we last talked about this kernel 5.4.1 has been moved into place in current. I updated and unblacklisted amdgpu and all is happy now. We
just got 5.4.2 and all is still well. I have all the regulars built and installed for xfce now. I have WiFi and the desktop is happy now.

So things are looking good on my laptop finally.. :)

Awesome sauce!!!

And there was a vul just out pertaining to MitM with VPNs on multiple OSes, including OpenBSD. Patrick is really fast addressing security and that might explain why it's in the mainline now.

I'll have to go and look and run Slackpkg and update Lilo.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)

On 08 Dec 2019, Al said the following...

Shortly after I wrote that, kernel 5.4.1 was added to current. I did a slackpkg update and upgrade-all, removed amdgpu from the blacklist and
all is well now. We've since got 5.4.2 and I have my desktop running with all the usual bells & whisles now.

Life is good.. :)

Okay I just checked the changelog and see 5.4.2 (I'll move there in the next couple of days) but no mention of security related kernel matters. This has
to be handled by the kernel devs or mitigated manually, but as soon as that happens expect an update soon thereafter.

The inclusion of the 5.4.x kernels just says upgrades, so if it was related
to the security issue below it would have said so and included the CVE number with a link to mitre.org

Here's some decent coverage on that vul: https://www.bleepingcomputer.com/news/security/new-linux-vulnerability-lets-att

Okay that didn't go so well... Hang on....

https://bit.ly/2LycLk0

There, lolz.

In the case of slackware-current it looks really good to me. I don't know exactly what Pat is shooting for so it may take a while yet, but it's all coming together nicely.

Yah he's taking quite a while making the soup this time. Just don't get
caught up in that guessing game - no one is ever right, like a football pool that no one wins lol.

I learned a long time ago to just ignore all those questions about, When is
the next version going to be released?"

My answer used to always be: switch to -current and don't look back.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)