Clueless end user since 2015 (14.1), using old Thinkpads without shiny new hardware.

The laptop I use for actual stuff stays on Slackware 14.2 32bit until the summer (end of term, I'm a teacher). I'm using xfce4 without KDE installed and half a dozen slackbuilds.

The testing laptop goes from -current to 15.0 by changing the slackpkg mirror. I quite like a full install with KDE package set plus Open/Libre office.

When you clever people sort out all the issues (say July/August) I'll do a backup and clean install on the 'production' laptop for September. Might treat myself to a slightly newer recycled Thinkpad at that point.

2 members found this post helpful.

1. champagne!
2. party...
3. clean install after the dust settles somewhat.

Thanks to ponce ( kudos o/ ) the SBo-s won't lag for half a year like before

2 members found this post helpful.

x86_64

1. Add 15.0 alongside 14.2 and -current (and other OSs on the same drive - I have plenty of unallocated space.) Take my time to set it up as I want it, including adding a few of AlienBob’s packages and a few Slackbuilds. This will be my daily driver.

2. Keep -current in order to keep testing it, but update at a slower pace - everytime an update is explicitly flagged as a security update, maybe once in awhile if some other update looks interesting ex. browser feature-only update.

3. Slowly migrate what I have on 14.2 to 15.0. Once I’m satisfied it’s done, delete 14.2.

Aarch/ARM

1. Install Aarch, once it’s released, onto RaspberryPi4. Probably -current, but maybe 15.0.

2. Slowly migrate/recreate onto Aarch on RPi4 what I have on ARM -current. Once I’m satisfied it’s done, delete ARM.

3. RaspberryPi Zero 2 W - TBD.

I will do a fresh install on my desktop (from signature) and stay at stable on the next cycle.

The two laptops get 15.0 release. Desktop remains on current.

Desktop/Laptop = stay on current
Servers = Upgrade from 14.2 to 15.0

Waiting for GIMP stable branch to require GTK+3, so I'll probably move to slackware-15 at that point.
Until that happens there's no real reason to make the move, still using GTK+2 desktop here so.. not in a rush to make plans.
FWIW kernel-5.15.15 builds fine on 14.2 and latest openssl-1.1.1m also builds fine on 14.2... KDE and new XFCE does not interest me, so whatever.

This appears to be my first post on linuxquestions, so hello everyone. Been using slackware for a very long time, I think from just before the turn of the century. I'm a bit of a heretic though, as I prefer MS Windows for my desktop UI and use ssh/putty to work with the 'nixes. I have in the past used X on a separate keyboard and monitor but it just feels too cumbersome having two keyboards on my desk, with one going to one set of monitors and the other going to another.

Plans... well, I'll download the dvd isos and keep them up on a torrent for a while. I recently had one slackware computer die of old age on me that I've replaced with a sparkly new i3 with 17 TB of storage. Its running a stock slackware 14.2 right now just to make sure the hardware is ok. I'll install 15 on it as soon as I write a USB stick for it. Then I'll actually get down to configuring it to replace the functions of the machine that died. Also need to setup a VM for testing; then I'll get around to doing fresh installs on the other machines that have slackware on them.

3 members found this post helpful.

Stay with -current.

The fact is that -current is an incredible development release

@Pat, you have to make -current unstable if you want people to move ! (from what I saw you just have to upgrade python3 )

... maybe it's planned :-)

2 members found this post helpful.

No plans. I'm sticking with current. The three main annoyances are ZFS needs rebuild with every new kernel, an updated kernel won't boot, and big DE is borked when its myriad small dependencies change. I've managed to mitigate all three and really see no need to get stuck on stable, especially if there won't be a major update for 5+ years.

Aside from ZFS modules needing rebuilding, staying with current has not really caused me too much extra work. With new kernels consistently automatically found by rEFInd, there is very little hassle in big updates: i. e. no more grub/lilo update disasters rendering systems unbootable. I've given up on all DEs except for XFCE, which works best all around, and CDE which is a bit of silly nostalgic fun. (Tried MATE, but caja has some show-stopping bugs that just keep coming back: try copying a large number of little files from one drive to another and it will probably take a month.)

1 members found this post helpful.

Clean install of 15.0 on one unit and the other units will stay on -current.

1 members found this post helpful.

I have been a Slackware user on all of my desktops since 2004-05. Three years ago, I had issues with VirtualBox and couldn't get the features I needed to work with the kernel that came with 14.2. My kernel compilation and installation skills lacking, I was forced to stay adrift in other Linuxes ever since. Each day I had hoped the world would give a little slack, but it seemed to get a little worse every day. I thought I had seen Bob a few times while out and about, but was never able to make his acquaintance. Hope had come and gone.

What will I do with Slackware 15?

Get ZFS drivers installed and my ZRAID imported, install VirtualBox, office suites and whatever else I need for daily work.

I am a software system architect and web developer. I need to have the latest tool chains installed for all of that. primarily NodeJS, and Visual Studio Code.

I want to spend some time exploring the "Best Of" tools that are available for KDE. Now that I have learned to love some time saving workflows from Gnome 40 (thanks Dr460nized Garuda!), I want to configure stock KDE for the same luxuries.

I feel those things would allow me to achieve the most Slack in my life.

Thanks Pat for all your hard work; your toil is recognized and any Slack gained shall be reciprocated.

1 members found this post helpful.

Good question!

1. Fresh install on ASUS vivobook laptop (overwrite -current) on sda4. Keep 14.2 on other partition until I get everything working. Then, track -current (overwrite 14.2) on sda3.
2. Fresh install on Dell vostro 3500 laptop (overwrite 14.2).
3. Fresh install on IBM x3650 server (overwrite -current 15.0 rc1).
4. Have fun!

Well, the python3.10 thing... I still remember!