Hot dang! Just when I'm cooking some dinner! This will be perfect..

Celebration day as Slackware 15.0 is released! I will mark this thread as solved; probably a good idea to create a different thread for any subsequent work you are doing with 15.0...

1 members found this post helpful.

FANTASTIC !!!


Wed Feb 2 22:22:22 UTC 2022
Slackware 15.0 x86_64 stable is released!

After many years of keeping them fully upgraded to 'current'
all 3 of my 64bit systems (two intel DualCore, one intel i7),
are now 'locked-in' to slackware64-15.0 repository.

Perhaps someday if I get an i9 system I'll put slackware64-current onto it.


BTW... that's a hellofalot of 2s in the release date and time. ;-)

Many have tried before, but not succeeded. In all likelyhood this thread is looking to become a drifter, and perhaps where the release party is being held!

Time to install! "dinner" is ready, coffee is brewing, plans have been crafted. Install and post install, it will be a long night

So if one is intending to stay on current, just do nothing?

1 members found this post helpful.

Yep. If you are "up to date," you are done.

Buy a "Slackware Hoodie" : ✔️

2 members found this post helpful.

Is there a store back up?

I will keep on -current on my home computers (most modern) and slowly upgrade 14.2 to 15.0-stable on my work ones (which are older). I have learned to use and maintain -current in the last 3 years - it is really solid and I have never got a serious break. I keep -compat packages provided by AlienBob in my -current systems in order to avoid problems with shared libraries bumps. Maybe I upgrade -current less frequently, maybe monthly because kernel upgrades have been very frequent and takes me more time. I guess the next release cycle will be shorter, another reason to keep with -current. Another thing I also do: I make regular images of my whole system with clonezilla, and if something goes awfully wrong I can always go back.

Thank you again, Pat and crew. Now you take some well deserved rest!

1 members found this post helpful.

Every Saturday for quite a few years now,
I have checked the slackware64-current repository
and then if needed executed these 4 commands via my bash script of 'slackup.sh'

slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system

Now that I've decided to stick with slackware64-15.0 for the foreseeable future...
it's gonna 'take some getting used to of _not_ doing that every Saturday.

;-)

1 members found this post helpful.

2022-01-19, 11:46
Well here is what I did. Removed my 14.2 mirrors. Added 15.0 mirror for x86_64 only, before I was also doing x86. That was pretty simple, just copied the slackware64 mirror over to a new slackware64-15.0 directory and updated the mirror as follows:
Modified my mirror scripts for multilib restricted alienbob to also mirror 15.0

Modified my 14.2 crontab entry to read:
I am the primary users of a laptop that belongs to a organization I am the Finance Officer of. With approval, I installed Slackware on it, it ran slackware64-current. I decided to switch to slackware64-15.0 for ease of upgrades. I bring it home to do upgrades from my LAN. I also modified my slackpkgplus.conf "MIRRORPLUS" entries to use 15.0 vice current.

Everything else will stay with slackwaer64-current.

I am still weighing if I should go through the trouble of doing a fresh install on this desktop. I probably will. Hoping that will resolve an issue with logging out from KDE to the CLI in which it does not finish dropping out to the CLI. I have to ssh in to the computer from my cell phone to reboot. I am not a fan off reset buttons or just turning it off unless I have no choice.

I'm new to Slackware (again), and it does seem to make alot of sense to stick with -current in many cases. I'll get 15.0 up and running on all my systems and familiarize myself a bit more with Slackware 15. But I'll be running a -current as a dualboot on my old laptop at first, to try to learn how to go about -current and running current, and once that's done, I guess I'll be running a dualboot (or VM) -current on my "current" laptop to get comfortable with it.

Anyways, I've heard nothing but positive things about -current, and alot of people seem to just prefer using -current. Seems pretty great, except for me, I would be on shaky ground at first

@zeebra

Don't worry. Keep your eyes on Slackware's Changelogs, see what's coming and upgrade as soon as you feel you are ready. Upgrades are frequent, almost daily. If you feel insecure, wait some days. Download and install AlienBob's -compat packages (icu4c, poppler and boost) from his current repository. If you use Sbopkg, get the new version from willysr (0.38.2) that works better with current repositories. And always follow linuxquestions.

1 members found this post helpful.

I have not posted for a long while, but on the occasion of 15.0's release, I decided to post an update. Life has been hectic here, and so no time for posting. Sorry about that!

Feb. 2nd is a day that will live in infamy; after too long an interval between -stable releases, 15.0 is here for our enjoyment at long last!

As some of you may know, I have a cluster of Mac Pro workstations that I got on the cheap; after Pat's inclusion of icecream, a package intended for clustering computers, I decided to embark on my own journey to create a cluster of my own. At that point, I hadn't had the pleasure of owning any Macs, so I decided to mosey on over to eBay to see what I could do to rectify that situation. Apparently my timing was fortuitous; a company was getting rid of a bunch of old Mac Pros, at fantastically low prices (~$25). Most of the cost I incurred in obtaining these Macs was the shipping cost; Mac Pros are heavy beasts, and shipping was accordingly beefy (~$80). After getting them in, I went again to eBay, and using a Low End Mac article, I was able to ascertain what type of RAM these beasts used, and was able to get them at next-to-nothing cost.

I had gotten tired of constantly updating all of these machines when -current changed, so I promised myself that I'd wait until 15.0-stable was released, install it to one of these machines, and then use a hard drive duplicator to mirror the image to all of the Mac Pros' hard drives. And now that 15.0 is released, now all I'm waiting for is my hard drive duplicator to arrive, so I can implement my plan.

As for my daily driver, I have decided that since 15.0 includes all of the software I desire, I will switch over to -stable until such time as an interesting addition appears in -current (interesting meaning desirable addition).

Happy Slacking, everyone!

1 members found this post helpful.