Slackware 11.0 Details

[Michael]

In the Slackware current change-log are now a few references to the upcoming Slackware 11.0.

In other news, I am aware of the expat-2.0 release, but this has a couple of API changes (and a new major library number) and it will take some time for upstream sources to patch for it. Therefore, expat-2.0 will not be used for Slackware 11.0 (but might be included in /testing).

I considered using --prefix=/usr here since X.Org will be moving from /usr/X11R6 to /usr when Slackware absorbs the modular release, but I think it will be best to wait and make those changes all at once. This, BTW, will be sometime after the 11.0 release. This current to stable cycle has already taken too much time (10.2 is in need of replacement), and introducing changes that might break things at this point would be foolhardy. Although there's still quite a bit in the TODO queue here I'm making my steps carefully as -current is very stable, and I think it should ship as a stable 11.0 soon so that we can get back to the business of breaking things in -current. :-)

ftp://ftp.slackware.com/pub/slackwar.../ChangeLog.txt

[Shadewalker]

I'm really looking ahead to this. Running -current as-is and it's very stable. Still wondering if 2.6 kernel series will make it in as default by 11.0. I'd hoped the modular X.org would be in as well, but oh well.

[Michael]

Slackware 11.0 RC1 has been released.

There are still a few changes yet to happen, but let's call this
Slackware 11.0 release candidate 1. :-)

http://www.slackware.com/changelog/current.php?cpu=i386 (Change log)

[1c3d0g]

Pat should start taking out old crap software in his distro that nobody uses. and include a proper, distro-maintained package manager. Until then, I won't be installing Slackware anytime soon.

[Patrick]

I've been using -current for a few years and it has been great. During the initial package selection the user has plenty of control over which packages to install; just select the 'menu' or 'expert' option. The package management does what it should imo. This minimalist structure was one of the key reasons that I settled on slackware after trying redhat/mandrake/ubuntu/gentoo/collegelinux. After the installation I installed swaret to simplify upgrading, but it still accesses a distro-maintained repository.

[Michael]

Slackware 11.0 RC4 is now out. Details @ http://www.slackware.com/changelog/current.php?cpu=i386

[Pritorian]

I'm pretty new in the Linux game, and therefore used a lot of time find the distro that fits my needs the most, and that is without a doubt Slackware for server usage.

I love the back to basic no frills configuration etc, as it never just suddenly breaks down on you, like a lot of newer highly automated system do(MS Windows Server and Ubuntu).

Slackware is without a doubt a pain to configure the first time around, and you will have to do A LOT of digging in both config files and manuals to set things up in the way you want it, but in the end, i haven't found any distro that i feel comfortable with, with regards to more or less mission critical server applications.

Yes, SlackWare is a pain in many ways, but it is also a superior distro i others, and i hope that SlackWare 11.0 brings the distro forward, without loosing it's main attractions. Wich i find it hard to belive Pat would ever consider doing.

[Michael]

Slackware 11.0 just got released @ http://www.slackware.com/announce/11.0.php

[Scott]

'Bout damn time Slackware 11 was released, and an official DVD iso is also a useful addition

Happy Slacking!