Slashdot Mirror
Slackware 11 is Coming
ejd3 writes "In the slackware-current changelog Pat has stated that '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. :-)' How much longer will the slackers have to wait?"
Slackers just run what's in -current
IMO Slackware is still the best Distro. I've been using it since 2.3 back in the 1.0 kernel days. I love its simplicity; it's designed so you can edit the config files yourself, none of the GUI tools so many distros like now with the actual config files hidden all over the place.
I doubt that... Never tried Slamd64, but maybe Patrick could make it some sort of "official port" or something like that... I've heard Slamd64 was rock solid and very "conservative" (maybe that's not the right word to use, but what I want to say is that it follows Slackware's path/philosophy).
- English is not my native language, so please excuse me if I mess things up -
I love Slackware. Other then a brief gentoo thing, I've used nothing
but Slack since putting it on my 486. But shouldn't this topic have
come out next week/month/year when Slack 11 is *actually* released?
It'll be ready Real Soon Now. Let's really discuss it then.
Think it'll have 2.6 as its default? Huh, huh, huh?
--User0x45
I had to switch to gentoo then ubuntu just to use my AMD64...
All you need to do is rebuild your kernel. A Linux distro is just a bunch of programs and config files, its not 64-bit specific.
You could use Slamd64. But regular Slackware will work fine on an AMD64: I believe that Pat is using one as his development machine. He wrote somewhere that he tried compiling 64-bit versions of various things, but he didn't see any performance improvement from it, so he abandoned the experiment. Of course it would be a different matter on a high-end server with lots of memory, but that's not Slackware's target market.
It's true that you don't need a GUI to configure Ubuntu. However, in my experience, if you're used to Slackware, the location of some config files in Debian-based distros can seem counterintuitive. Slackware is very simple once you understand it; I especially like the BSD style init system, it just makes sense.
Don't get me wrong, Ubuntu is great too (I'm using it right now), and I haven't had much trouble configuring it the way I want. But after using Slackware regularly for a while, I can understand why he feels the way he does.
What's the ugliest part of your body? Some say your nose, some say your toes, but I think it's your mind. -Zappa
I've seen a few comments above from people saying that Slackware makes poor economic sense. I say it can make economic sense in many cases.
/etc/init.d though?).
Slackware is a distro, like any other - and just like any other distro you tend to have to be familiar with it in order to get things done efficiently. However, what Slackware does let you get away with is to update packages direct from the developers without having to worry about exploding the "package database" or maintainance system. If you want "fancy" package handling systems you can use the likes of slapt-get or similar. Slackware won't tear you apart or breakdown into a locked up mess if you install something from a "non-slackware-approved" source package.
The default relative daemon sparseness of Slackware makes it quite easy to keep an eye on, especially if you're trying to keep an eye out for malicious things. The whole start up script system is rather simple enough too (will we get a soft-linked
That said, there's a few things which I wish were included by default in slackware (and perhaps will be in the future) but no single distro is perfect. Nearly all distros require some degree of tweaking.
Best of all though, Slackware is quick to download, quite often you only need the first ISO and you've got yourself a fairly comprehensive system ready to go, for someone who knows what they're doing.
There are a couple of slack-based AMD64 systems besides SLAMD64. I liked SLAMD64, but haven't found it as trouble-free as some others apparently have. Frugalware claims to be pretty much Slackware with Pacman bolted on, and I liked it a lot. I also just downloaded something called Bluewhite 64 Linux, another unofficial port. That goes on my testing partition this weekend (replacing STX Linux, another Slackware derivative I was testing for installation on a friend/potential convert's older laptop).
So if Slackware is a niche player now (which I don't believe), then one part of that niche is as a base for new distros -- the excellent Zenwalk (which I run on my laptop), STX, Frugalware, Voltalinux (Slackware with pkgsrc?), Slax and Vector, just off the top of my head. Not as many derivatives as Debian, perhaps, but certainly a healthy number and probably indicative of a healthy distro.
I think Slackware's biggest "problem" is that it has little to no "community," at least as far as vocal fanboys (you know, the kind who visit Distrowatch to click through and drive up its numbers). I think it tends to attract and keep a self-sufficient, quieter crowd, and therefore its presence isn't as great as its numbers, if that makes any sense.
And text, of course. As soon as I boot up and people see text instead of a pretty splash screen I see that sphincter-tightening look come over some of their faces.
But beyond the entertainment value it's probably a bad thing.
Other than noting that he is recovered, none that I've noticed. A private person, which I respect.
If you want your life to be different, live it differently.
...it doesn't have a PR machine (even a volunteer one) behind it cranking out a steady stream of news. Look at Distrowatch Weekly's upcoming releases and announcements, and you see release roadmaps, schedules, plans, estimates and pre-order information going all the way out to December. Slackware is nowhere on there.
Even on userlocal.com, supposedly the Slackware community site, and the top items are from February and April (and the latter's about Zenwalk). Other distros start work on their next release before the current one is final, and we hear about it from one release right to the next. Hell, we heard about the Suse and Ubuntu delays for what would seem like forever if we didn't have all that "when is Debian going to release" and "Vista delayed again" coverage to compare it to. So Slack gets a RSN item on Slashdot. Seems small in comparison to all the coverage of alpha flights, umpteen betas, RCs and golden masters some distros get all over the web.
Personally, I'm happy to be using a distro done by a guy more interested in getting a solid product out the door than getting a good press release out the door.
It makes perfect sense, as I'm one of those of whom you speak. I'm a UNIX professional who works with Solaris, OpenBSD, FreeBSD, and Redhat AS. I run Slack on my workstation and on a couple of smaller servers because it is about as unobfuscated (at least from my perspective) as you can get. No glittery anything, just a very solid Linux.
I need to send Pat money this time around as well as I think I purchased 10.1 but not 10.2. Anybody who seriously uses Slack should do the same if they can afford it. He puts out solid distro, and he's a nice guy.
I think Slackware's biggest "problem" is that it has little to no "community,"
there is a huge slackware community, it's just very much like the BSD community. WEare simply too busy using it in embedded systems, and other places to take the time to run around posting to all forums "S1ac4war3 0wnz joo!" messages.
Slackware is the absolute best distro for doing really advanced things like stuffing it in an embedded device or making a super stripped down machine that makes an old useless 486 scream like a monster for a single important task... makes the best OS for a homebrew firewall that fits on a 8meg CF card.
I use it for developing apps for the gumstix embedded platform. installing the cross compilers for alpha processors is painless compared to a rpm or deb based distro.
Do not look at laser with remaining good eye.
I too am a fan of Slackware, and am typing this on a Slackware 10.2 system with a 2.6.16.9 SMP kernel (built from the kernel source), to support one of those new dual-core Pentium 4 gizmos. In other words, it goes like stink...
Even though I can download the CD images, I always buy a copy of each new release.
It's not a crime for a Linux system to look like Unix, and if your hardware barfs over a text-based install, you really do have a problem. I like being able to download source (including kernels), build it and it just works. I still have nightmares about the time I tried to help somebody upgrade a kernel on a Fedora Core box. Shudder.
Slackware isn't a pre-packaged Linux system in a can: open the can and pour it out, ready to go. It's a construction set for building any kind of Linux system you want. And it's all the better for it.
Thanks, Patrick.
...laura