hiya,
just donated to store.slackware.com, that's easier than providing immortality to the bdfl or endlessly playing the guessing game on the next big release
ta

2 members found this post helpful.

Every........Single.......TIME!

Why can't we just have FAQ, stickied here and this should be finally addressed?

Q: When will (insert version here) be ready?
A: When it's ready.

1 members found this post helpful.

Yeah but when?

Reading this thread made me really want to buy a Slackware mug and bottle opener. Hopefully Slackware 15 will lead to new sales of those.

2 members found this post helpful.

It's just about how excited we are while we are waiting for the NEW GLORIOUS Slackware release! Maybe with a small impatience It has nothing to do with the release day D (at least that's my impressions).
It's just a game/ritual.. and BTW I love it

When do I expect Slackware 15? Dunno, the release isn't up to me. There's an old saying about wishing into one hand and bleeping into the other and seeing which one fills up first.

What do you expect from Slackware 15? Darth Vader to make some comments about the lack of PAM and/or something else he needs.

3 members found this post helpful.

Well, for at least about a month or more now:


Welcome to Slackware64 version 15.0 (Linux kernel 4.9.67)!

If you need to pass extra parameters to the kernel, enter them at the prompt
below after the name of the kernel to boot (huge.s etc).

In a pinch, you can boot your system from here with a command like:

boot: huge.s root=/dev/sda1 rdinit= ro

In the example above, /dev/sda1 is the / Linux partition.

To test your memory with memtest86+, enter memtest on the boot line below.

This prompt is just for entering extra parameters. If you don't need to enter
any parameters, hit ENTER to boot the default kernel "huge.s" or press [F2]
for a listing of more kernel choices. Default kernel will boot in 2 minutes.

I noticed that when I installed Slackware64-current on a new machine a couple of weeks ago. I did a double-take, checked the change log, came here to see if 15 had been announced, and found nothing. So I figured it's a hint that 15 is coming soon. When it's ready, of course.

If 14.2 is used as an example, 15.0 could still be over a year away. Slackware 14.2 was released on 30 June 2016, yet the etc package was updated to 14.2 back on 21 April 2015.

Let's hope we don't have to wait that long

when: when it's ready of course

what: to stay fully backwards compatible with 14.2. I had some troubles setting up certain things in 14.2 (not slackware's fault), I just want to be able to repeat the same workflows in 15 and get a working system faster

I suggest to move i3 to official repository/installation option for 15, because it works very good, I always use it:
https://slackbuilds.org/repository/14.2/desktop/i3/
Also, I totally agree with other person who suggested to replace Blackbox with Openbox.

1 members found this post helpful.

OpenRC, Qt5, Qt5ct, Qemu.. maybe a kernel-vm so that kernel-huge is not as huge.
Inclusion of MC in bootable installer environment.
/kdeL/ for /l/ part which is only used by kde.

I'm not concerned with when the next release of Slackware is completed. I would like it to possibly be easier to have an environment that includes or make including rust easier so that I can compile my own Firefox but that largely depends on the bigger issue for me which is having a clear cut, simple option to omit Pulseaudio and have an alsa-only system. That seems to depend on expanded apulse function so I'm not holding my breath.

FWIW even with that nasty Pulseaudio intrusion I have yet to be altogether disappointed in any Slack release since v7.

You'll definitely be a happy camper with the next Slackware then...

https://packages.slackware.com/?r=sl...1-x86_64-2.txz

That is good news but I am actually more interested in being able to do without Pulseaudio which I have come to despise after actually trying to like it. I find it a stumbling block almost weekly, sometimes for days in a row, and certainly monthly at least up until recently. I understand it has appeal for the lowest common denominator, embedded audio, but I actually love Sound and have spent large sums to insure that I get very close to the best possible. That is substantially degraded by Pulseaudio and would be degraded further by some cheap embedded audio chipset.

1 members found this post helpful.