Slashdot Mirror
Slackware 12.0 Released
Matt writes "Straight from our good friend and colleague in the fight for quality distributions, Mr. Patrick Volkerding, comes a brand-new and eagerly-awaited release of Slackware, version 12. HAL automount, KDE 3.5.7 and XFCE 4.4.1, Xorg 7.2, 2.6 kernels as far as the eye can see, oodles of updated applications and utilities, and hardware support for just about anything under the sun. Get it here. Enjoy! I know I will."
Once you go Slack, you never go back!
Well that used to be my motto, at least for my servers. But I really just got tired of having to compile things that I could not get with slackpkg or slapt. I have switched to Debian for my servers I alleviated my headaches with compiling apps (those not included or available). Mind you if you needed something that WAS available with slackpkg or slapt then it was a great system. And even still a better system to have a locked down tight server. I would rank it up there with Gentoo in certain aspects (of course not installation).
Since I will probably quest to install Slack again someday, does anyone know if it comes with a GUI installer yet? I have not installed since Slack 10 so maybe my question is obviously dated, but it is a valid one at that!
-- Brought to you by Carl's JR
I have work to do tonight! Don't make me choose between that and upgrading to 12.0!
Slackware Package websites:
www.linuxpackages.net
www.slackware-current.net
(There are more, but these are easy to remember.)
They're very nice for any omissions and/or upgrades between release versions.
-Tom
Cleaning out my garage a week or two ago I was going through an old box and ended up tossing a set of Slackware A floppies... That was such a refreshing change from downloading a boot disk and bootstrapping a system starting with compiling GCC.
I know its only peripherally related to the article, but man. V12 of Slackware? Time has flown, and things sure have changed.
> It is a bit hard to jump back into Slackware... The long hiatus a while back left me seeking other distros which I have stayed loyal to.
No, you're probably not the only one. However, that opinion is the opposite as that of Jason1729 below, who states he gave it up due to too many updates and fixes, and he's probably not the only one to feel that way either. Between the two, Patrick is probably running at pretty much the right speed:
From: Patrick J. Volkerding (bf703@cleveland.Freenet.Edu)
Subject: ANNOUNCE: Slackware Linux 1.00
Newsgroups: comp.os.linux
Date: 1993-07-16 17:21:20 PST
The Slackware Linux distribution (v. 1.00) is now available for
anonymous FTP.....
12 versions in 14 years, plus revisions between. All under his guidance. Most would have abandoned the effort sooner and with fewer releases, and probably due to doing so many in that time. Hell, most would have given up rather than rewrite it all in order to switch libraries.
"I may be synthetic, but I'm not stupid." -- Bishop 341-B
Oh my lord, did you just end a sentence with a preposition?
Yes, when it does not have what I want. Which is far too often.
Where Debian (and Ubuntu) "win" on the desktop is not because they have the best package manager tools, its because they have the most packages. I originally switched to Ubuntu back in 2004 because it was the only Linux distro (besides Debian unstable of course) that had a program I really wanted (bit tornado) in its package repository. Thanks to this huge repository and Ubuntu, I have gotten EVERY linux program I have wanted over the past three years without touching a complier. Heck, I haven't even had a compiler installed in the last year.
I know that ruins the effect of Linux for some, but compiling programs and chasing dependencies is the worst part of the OS for me (and other like minded desktop users). Each to their own...
Open Source Sushi
That isn't unique to Slackware by any measure. Even Debian, with its fat 14-CD install set, can't include everything. You are more likely to find what you need in a Debian package, but once you step outside the repository, it's tough going. With Slack's simpler layout and simpler package tools, at least you have a chance when rolling your own.
AFAICT, there is no silver bullet, only trade-offs. Even Windows will get hamstrung by dependencies if you stray too far from the mainstream, though commercial Windows software often packages tons of OS updates with it, solving your dependency problems but often breaking previous software installs. Debian's repository is a walled garden, and they try to mitigate the pain of the walls by making the garden really, really big. Slackware is all open, but that leaves you on your own sometimes. RPM-type distros are somewhere in-between. Choose distro most suited for your needs. If, like me, you want to do lots of oddball stuff, automated package managers create more problems than they solve. But if you can live comfortably without ever installing things outside the repository, then Debian is for you.
If you learn Ubuntu, you know Ubuntu. If you learn Slackware, you know Linux.
I think, therefore you are.
Well, definitely not up to you to decide. The site is mine. I already told Patrick about this. I do respect the man, and therefore if he asks me to remove it - I will. So far his reply was something like that he doesn't have time for such things right now, and later he will contact me. Besides this, what bothers YOU personally? You're holding the trademark, or what?
$ cd
/home.
$ dd if=/dev/zero of=8G bs=1048576 count=8192
I dare you to tell me that command failed on your system, with space remaining on your partition containing
One of the defining points of Slackware is the small set of official packages it features. On top of that, the native package management tools don't track depencencies and don't have the notion of remote repositories. All together, this doesn't adapt very well to users who want to try new software all the time and spend their days installing and removing packages. Doing that is hard with a vanilla Slackware, so people have created tools like swaret or slapt-get to simplify the process and be able to use remote repositories like the one at linuxpackages.net and similar, where they can download many unofficial packages that sometimes include dependency information slapt-get can use. I don't think that's "right". Let me explain. It's cool that Slackware is flexible enough to let you do that, but your system ends up in a very chaotic state after some time, in my experience (specially if you use slackware-current instead of slackware-stable). You can manage your system that way if you want, and maybe you're careful enough to do it, but it's very hard. That type of users would probably be happier with Arch, Gentoo or even Debian (I never understood the rivalry between Slackware and Debian; I've used both and both are great in their styles).
Patrick Volkerding probably thinks that way too, because he doesn't include those tools in Slackware. If I recall correctly, swaret was included for some time but in the end it was removed. He includes, however, a tool called slackpkg, which is clearly targetted at more "classic" Slackware users, because it lets you use one official mirror and manage systems composed of official packages for the most part, and includes some mechanisms to let you have some custom packages without being a headache (maybe downloaded from linuxpakages.net or slacky.eu or built with your own slackbuild scripts that you can also download from sites like slackbuilds.org). The problem is that slackpkg is slow (it's a big shell script), and doesn't let you track many corner events that happen frequently in slackware-current, so that's the starting point of slackroll.
Think of it like slackpkg on steroids. I specifically designed it to detect situations which are frequent in slackware-current, but it can also be used for slackware-stable without any problems. By design, it can:
And more stuff. Like I said, slackpkg on steroids. It's much faster, uses less bandwidth, detects more events and it's probably more flexible. I'm pretty satisfied with the result, so I wanted to invite people to read the program's webpage and try it if you think you fall into the target audience. It would be fine if I was the only user, but more eyes mean less bugs and I think it's always a shame when you create a tool which you are proud of and SourceForge only shows 20 downloads because people do not actually know it exists. Its main problem is that the initial setup may be more complex than usual and you need to read a bit more to know how it works. Howev