When will Slackware 15.0 be released?

duncan_roe · 08-03-2021, 12:44 AM

Quote:

Originally Posted by slack-uke

as a practice, when we do a major upgrade of a server we bring on new hardware and switch things from a firewall.

Thus the replacement servers are new installs with proper re-compiled 3rd party packages and/or replacements -- just saying

we were not born yesterday -- I have been programming since the 70's. where you alive then?

WTF? I simply pointed out that UPGRADE.TXT needs updating. Perhaps you quoted the wrong post.
BTW I was programming in the 60's

keithpeter · 08-03-2021, 03:21 AM

Quote:

Originally Posted by slack-uke

I have to say as all of us were early adapters of slackware, have been frustrated by a lack of a stable version since 2016 has opened us to attacks by the Russians.

Apologies for off-topic post, and good luck to you in your endevours.

Just wondering if putting a cdn in front of the Web server would be part of an answer to ddos problems?

rkelsen · 08-03-2021, 05:08 AM

Quote:

Originally Posted by slack-uke

I have to say as all of us were early adapters of slackware, have been frustrated by a lack of a stable version since 2016 has opened us to attacks by the Russians.

It might be old, but it is far from unmaintained. The latest security patches for 14.2 were uploaded on 21 July... Less than 2 weeks ago.

It has been actively maintained and patched since release, much like Windows 10... Which, incidentally, is nearly 12 months older than Slackware 14.2.

So... Drop the hyperbole.

enorbet · 08-03-2021, 10:12 PM

Quote:

Originally Posted by slack-uke

I have to say as all of us were early adapters of slackware, have been frustrated by a lack of a stable version since 2016 has opened us to attacks by the Russians.

Sooooo... can you cite even a single example of a server running Slackware that has been compromised by the Russions (or anyone) directly caused by some flaw in Slackware?... or is this just paranoid speculation bordering on FUD?

If you actually have a documented example, or even if you are rightfully paranoid, I'd suggest better isolation between internet and intranet. A complex, layered subnet architecture would help or, even better, a dedicated hardware firewall is always a good start regardless of intranet and/or server and workstation OpSys/Distro.

bassplayer69 · 08-04-2021, 05:47 PM

Quote:

Originally Posted by slack-uke

We are the customer -- running a non-profit website that needs to withstand the best the Russian government can throw at it. We withstood many DDoS and still remained running -- thus the need for a stable version we can build on.

We survived the Orange Revolution & EuroMaidan attacks and that continue to this very day.

We need a solid base to build on -- hard to do when the base is either dated or shifting.

Just saying.

I use the same OS for my profession which is engineering. My colleagues for the non-profit are all engineers -- we approach things in a systematic manner.

Slackware met our needs but lately is sliding in our inability to recompile updated 3rd party code to secure levels.

Thus saying slackware as a base os has failed. I have initiated a search of alternative linux-based OS.

I have to say as all of us were early adapters of slackware, have been frustrated by a lack of a stable version since 2016 has opened us to attacks by the Russians. Even worse over the last 25 years had recommended slackware as a secure route for other open source / pro-democracy entities in Ukraine.

My faith is dwindling

I know this is a Slackware website, but you might benefit more by running a LTS linux distro or another distro that has long term support and is hardened down. Maybe even a variation of BSD? Just a thought.

Pithium · 08-04-2021, 09:58 PM

I think 15.0 should be released on a Saturday. The following Sunday can be Patrick's Day of Rest. Since we worship The Slackware Way anyway we might as well go all in!

Franklin · 08-05-2021, 05:16 PM

Quote:

Originally Posted by slack-uke

Would it help if a plan was verbalized as the goals for the 15.0 release instead of a constantly moving goal post with unknown acceptance criterion? At times feel like Linus with Lucy and the football.

I think this is an interesting question, though I might have phrased it differently.

Hypothetically, suppose Slackware 15 drops September 1. How much better would 15 be on September 1 vs. July 1 (the anniversary of 14.2) or August 1 for that matter? Are there specific things that are being tested or waited on?

I'm perfectly fine waiting, but I'm curious what I'm waiting for. Is there a "plan" as slack-uke puts it? I'm sure there is TBH, but I think it would be interesting to hear snippits of the thought process. I think it would help prevent a lot of the "Is Slackware Dead" stuff too. (probably not ...)

Will the answer mean anything to me? Nope, but it would be interesting to hear. And I think occasional blurbs might be financially beneficial as well - I know I joined the Patreon after PV's post in November. Hearing occasionally from the BDFL (or someone on the team) could go a long way. Yes you post here, but not what I'm describing and not consistently.

I'll go back to lurking now.

zeebra · 08-05-2021, 07:35 PM

Quote:

Originally Posted by Franklin

I'm perfectly fine waiting, but I'm curious what I'm waiting for. Is there a "plan" as slack-uke puts it? I'm sure there is TBH, but I think it would be interesting to hear snippits of the thought process. I think it would help prevent a lot of the "Is Slackware Dead" stuff too. (probably not ...)

If you read the changelog there are a few things that need to be sorted out before a release candidate can be made. Not sure the MariaDB issue has been solved.

It's not waiting for something as far as I understand, more finding ways to make everything in "current" perfectly work as desired. There is nothing in the changelog to indicate "we need for wait for glibc version xyz or some software version xyz before we can freeze", so it seems more a matter of getting everything that is there currently optimized. But while that is being done, new versions of xyz is also being released ofcourse.

Quote:

Sat Jul 17 17:55:10 UTC 2021
Not quite ready to freeze things for a release candidate, but getting there.

hitest · 08-06-2021, 06:30 PM

Quote:

Originally Posted by slack-uke

Thus saying slackware as a base os has failed. I have initiated a search of alternative linux-based OS.

I understand. I suggest that you wait a while before you jump ship to another distro. You know that you'll be re-installing Slackware 15.0 when it's released.

andrew.46 · 08-07-2021, 03:40 AM

It has to be released very soon as I have just purchased a new (old) laptop and I am going to install the latest release version on it. No pressure PV

allend · 08-07-2021, 10:52 AM

It has been a couple of months since I did an install from scratch of -current, but the installer has had some love since I last used it. My thanks for that. On a 64-bit UEFI system, when the install is completed after rejecting LILO and eLILO installation, you can drop to a shell and install the GRUB bootloader with

Code:

chroot /mnt
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB
grub-mkconfig -o /boot/grub/grub.cfg

When the email to root re the defunct Linux Counter project disappears, I reckon we will be close to the bottom of the TODO list.

hitest · 08-07-2021, 02:09 PM

Quote:

Originally Posted by allend

On a 64-bit UEFI system, when the install is completed after rejecting LILO and eLILO installation, you can drop to a shell and install the GRUB bootloader

Yes. I love GRUB on my UEFI system, it works very well indeed.

ZhaoLin1457 · 08-07-2021, 02:22 PM

Quote:

Originally Posted by allend

It has been a couple of months since I did an install from scratch of -current, but the installer has had some love since I last used it. My thanks for that. On a 64-bit UEFI system, when the install is completed after rejecting LILO and eLILO installation, you can drop to a shell and install the GRUB bootloader with

Code:

chroot /mnt
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB
grub-mkconfig -o /boot/grub/grub.cfg

When the email to root re the defunct Linux Counter project disappears, I reckon we will be close to the bottom of the TODO list.

Then, Slackware already solved the SecureBoot compatibility?

Franklin · 08-07-2021, 03:44 PM

Yes, I follow the changelog. For example, this is excellent from today:

Code:

Since glibc-2.34 makes a potentially risky change of moving all functions
       into the main library, and another inconvenient (for us) change of renaming
       the library files, we'll stick with glibc-2.33 for Slackware 15.0 and test
       the newer glibc in the next release cycle. But we'll backport the security
       fixes from glibc-2.34 with this update:[snip]

I love these little windows into the process. What I would like (and what I think might be helpful) would be for these explanations to live elsewhere as well. Perhaps the landing page on slackware.com and maybe part of a sticky post here in the "official" slackware support forum. Not all people looking at slackware.com for the first time know where this info lives and it could be helpful. We have recurring threads here for the kernel, nvidia drivers, KDE, XFCE - why not thoughts from the BDFL and team?

Also, even in the changelog, these comments are somewhat scarce. I know not everything deserves a blurb, but if once a month someone said something about the status of current what folks were thinking. Currently, I look at Eric's site, Willy's site, the change log, this forum - just trying to glean something regarding the path forward.

I know the important thing is the build, but I think some extra communication would be really helpful. Nobody can afford to put obstacles in the way of new customers, and certainly aggravating existing customers is equally unfortunate.

Anyway, that's all from me (again). Just felt today's update required an acknowledgement.

Daedra · 08-07-2021, 04:09 PM

Quote:

Originally Posted by hitest

Yes. I love GRUB on my UEFI system, it works very well indeed.

Same here, After I built my Ryzen system in December I was finally forced to use UEFI. I immediately disliked elilo, to each his own, but It was not for me. After experimenting for a while I have come to really appreciate Grub. However I also really like rEFInd. They both have there pros and cons which the author of rEFInd sums up perfectly with this post. The post is 5 years old so some of the points might be outdated, but most of it still seems relevant. I also highly recommend Richard Craniums SlackwareGrub2 script if you use Grub on Slackware. It gives you a much nicer menu than what is provided with the default Grub install.