Slackware 15.0 is coming out soon and I am curious as to what plans people have once the isos hit the servers.

My own plans are:

1. Install it on my new (old) Lenovo T460. This has a -current snapshot at the moment but the plan was always to have a really solid release version of Slackware in place.
2. Put 32bit and 64bit VMs in place and get some badly needed spring cleaning done on the 8 SlackBuilds I look after on SBo. I should really look after a few more scripts here as well...
3. Continue to follow -current. Whenever a release comes I always think about getting off the train but this time I am sure that I will stay with -current which I have followed for some time now.

So just some simple plans but I am curious to see what others have in mind?

First thing I'll do is upgrade my current to 15.0 for good. I really don't like rolling releases. Then I'll start fleshing it out with the non-standard things I need and have on 14.0 but don't want to put on current: stuff from slackbuilds.org mostly, but also Bob's multilib glibc, which I need for my printer driver (and the driver itself obviously). Once I have all that, it will become my main Slackware and default elilo boot. And good riddance to current and all those big updates!

7 members found this post helpful.

keep -current.

4 members found this post helpful.

remain on -current

4 members found this post helpful.

I plan on installing it on my laptop and wfh workstation, both of which are running older installations of current now.

I also plan on installing it on a server which has been lounging on my workbench for way too long. It will eventually go into a colo site. I installed 14.2 on it originally but would rather have more recent software on it.

It didn't occur to me until just now, but I'd might as well try installing 15 on the system where I'm trying to get Slackware to work with a Xeon Phi coprocessor card. I don't think the mpss kernel module has seen much development since 4.4.x, but when it finally does work I'll be wanting to develop software in D which makes use of it. The gcc-11 D compiler (gdc) which ships with modern Slackware is vastly more capable than the D compilers available for 14.2, especially its debug symbol support. I'll be wanting that.

1 members found this post helpful.

I didn't have too much trouble with -current on my laptop, except. I can remember 4 or 5 big problems in the past ~5 years.

But for the servers I am definitely sticking to 15.0 as long as possible.

My other plan is to brush up my slackbuilds with all the knowledge I have acquired in the past ~5 years and submit them to SBo. I like installing things with one command instead of a lot of work.

4 members found this post helpful.

Exactly! I cringe a little when I look at some of my older SlackBuilds (actually on SBo) and it is probably a good time to polish some of my 'my use only' scripts as well.

Can't wait, coming back to Slackware after years of MacOS (company issue) and Ubuntu.

Plan to install Slackware 15 on my lenovo legion laptop (purchased 2 weeks ago), wanted to install -current at first but since 15 is going to be out soon might as well just wait.

p/s: been away from Slackware for ~10 years

2 members found this post helpful.

FWIW I also have a background with Ubuntu which I am not ashamed of, there are many fine people in that community.

1 members found this post helpful.

I'll risk staying with -current for yet another Slackware development cycle, though I don't know how long it will take.

1 members found this post helpful.

I'll upgrade a few computers from 14.2. My extra 15.0 packages (mainly from SBo) are already built (on a -current computer) and ready to install. Then I will do a cleanup of obsolete packages.

I'm not sure whether I want to explore the KDE/Plasma world. KDE4 was horrible and I am quite happy with the simplicity of XFCE. KDE5 is also said to be quite efficient in using computer resources though, I don't know. I'll probably try it out and come back to XFCE .

1 members found this post helpful.

Install Slackware64 15.0 on my new computer.
Install Slackware 15.0 (the 32-bit version) as well.
Then, add “--current” to the mix, also both the 64-bit and the 32-bit versions.

There will, then, be five operating systems installed on this computer: Xubuntu 20.04 plus four Slackware systems.
When Ubuntu 22.04 is released, I will likely add a Xubuntu 22.04 system as well.

Once Slackware 15.0 is properly set up, I want to revisit my custom-compiled GRUB copy and install that as my boot loader. I’m not entirely sure how I can install a primary and a secondary GRUB boot loader on this new computer, which boots in UEFI mode. Under legacy BIOS, it was easy: I installed the primary boot loader onto the MBR, and the secondary one onto the boot sector of its own partition. I could then chainload the secondary boot loader from the primary one. (If you wonder why I want this secondary boot loader, I just like to mess with GRUB, and I can break the secondary copy without affecting the primary one. Hence, unless I do something really stupid, I can still continue to boot my computer.)

Not sure what I will do with my laptop, which I hardly use anymore. It has Xubuntu 18.04, Xubuntu 20.04, Slackware64-current and Slackware-current installed. However, my new desktop computer is so powerful and fast that using the laptop is getting a more and more painful experience. May get a new laptop, once AMD-powered 17-inch models become readily available.

1 members found this post helpful.

My plans will certainly depend on time availability, but here goes:

- Reload all my systems with 15.0. -current may still get run in a vm, but to be honest, it's exhausting following the development branch
- Try out s6 as an init replacement. I current run runit as my init.
- JACK-ify my system perhaps (jack-audio-connection-kit)
- Install multilib, WINE or such, and hopefully have some time to do a little gaming again beyond Urban Terror
- Set up SSO with OpenLDAP & krb5 or similar
- relax a bit after a couple years of following -current

2 members found this post helpful.

Because I want wayland to be fully functional with my Ryzen 7 (I still have a problem with hibernate/resume, and despite my research,
I clearly don't know if it's due to plasma/wayland or the kernel. No problem with my Intel i3 Lenovo L440 laptop ...)
I need to keep bleeding edge updates, so on -current

I will probably switch the Lenovo to Slackware 15.0, since ATM everything works perfectly

1 members found this post helpful.

Clean install of 15.0 on everything. Give -current a rest for a while...or maybe forever? See how I feel.

1 members found this post helpful.