I own two Slackware t-shirts. A Slackware hoodie would be perfect!

Unfortunately, your report came too late. Pat knew we were towards the end, saw your report, included the proposed upstream fix, and before you stated it didn't work, he had already finalized 14.2 and started the release process (even if we didn't see if until the next day). He wrote the changelog announcement of 14.2 on 30 JUN 2016 @ 20:26 UTC (which is around 4:30PM Eastern Daylight Time). You didn't reply to your thread until almost 24 hours later (1:50PM EDT).

He had the 4.4.14 kernel in there since 24 June, so it seems like if this was reported earlier, a fix that was tested might've made it in to 14.2. As it stands, he took the fix that was proposed by the upstream people and assumed it would work.

Unfortunately, bugs will always exist in stable products. Long development cycles like this one help to minimize them (and he did minimize a TON, especially these last few weeks), but they won't get rid of all of them. Luckily, your issue won't be a problem during a stock install (only upgrades where you already have that encryption set up). You can safely install Slackware, install the needed fix, then set up your encryption as needed.

2 members found this post helpful.

what's the difference between upgrade from 14.1 and a clean install?

In his case, an upgrade would likely have the encryption already set up, so once he booted up, it would fail to mount. On a new install, he would have to set up that encryption, so he could install the fix before he creates the encryption.

Well, I anticipated Pat would wait until 4.4.15 is released, so I didn't follow the thread very close, besides I was busy on a business trip this day.

But no hard feelings, I am happy that 14.2 is released and the worlds best distro still thrives

Sorry, I didn't notice that - my apologies

I also apologize if I came on too strong - I just think a new thread should have been started for the problem you have (had?)

I am glad to use updated Firefox

I have promised myself to not install 14.2 until my thesis finished. That will help me get rid of my damn thesis sooner.

1 members found this post helpful.

Whether you need my approval or not you have it, dear Hosein.

1 members found this post helpful.

Fantastic! Clean installed my home machines, now about to do my workstation. Has anybody used CUDA and the latest NVIDIA drivers on 14.2 yet?

The latest "long lived branch" Nvidia driver is 367.27, and it has worked perfectly with 14.2 (current) since its release.

Thanks, really looking forward to getting 14.2 up and running on this machine

slackware is the only distribution that keeps me from leaving linux and switching to openbsd.

and salutations to the slackbuilds team - providing slackbuilds for 14.2 without delay. you do an amazing job.

thanks to all of you.

1 members found this post helpful.

You can have both if you wish. At the moment I'm running a dual boot of Slackware64 14.2 and OpenBSD 5.9 on one of my Slackware boxes.

A little late to the party here. A hearty "thank you" & tip of the hat to Pat and the team for the stellar work they do. Eagerly awaiting my subscription dvd. I've been running -current for several years now, and the best just keeps on getting better. Slackware.....what else can be said!