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."
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.
if it still lacks a ports or packaging system that allows easy to update packages and conflict resolution, it's not worth the time.
If you mod me down, I will become more powerful than you can imagine....
Slapt-get install ... too hard for you?
Oh well.
Archives, you know we all can get at em'. You do understand there are tools to use your debby stuff elsewhere deb2targz being just one. What's a kernel structure and why just 2? We tend to roll our own kernels mostly.
If you learn Ubuntu, you know Ubuntu. If you learn Slackware, you know Linux.
I think, therefore you are.
What this guy is trying to say is that with Slack, you're going to have to use a terminal. Start with slack, get used to the terminal. You'll learn. You'll thank that random guy on /. that said 'Get used to the terminal'. Ubuntu is all GUI tools. When those fail (and they do), you have to go to the terminal anyway.
Yes, I meant to say 'terminal' several times in this post. Do you see a theme here? Welcome to Linux. (If this is your first Linux distro, try Slack, *then* try the others. You'll be back.)
$ 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
Or very educational, depending on just how stubborn you are. *wink*
I'm working for a company that had Slackware as its primary server OS. Until I showed how much time it took to operate and maintain.
Slackware is great for many things - single-purpose machines, getting that old P1 running, etc. It has a few major flaws that make it unusable in businessland:
1: too #$%) hard for a new admin. It requires a lot of arcane skills to get set up properly - skills that don't come cheap, and are hard to find in the marketplace.
2: No dependency management. Debian- and RH-based distros have had dependency tracking for ages, and the capabilities of up2date, yum, and apt-get are far in advance of what you can do with any slackware package management system. Plus, there is literally nothing in Slackware that matches RHN.
3: Proprietary software. Although with enough hacking, you can get a lot of it to run on Slack, the provider will not give you any support. And without that, you're hosed. We've ended up using RHEL on a Websense box because they would not recognize a bug that showed up in CentOS. You know what? The bug went away on RHEL.
Given all that, I still like Slackware as a Swiss Army knife-type distro that I can use for things where I don't have to maintain it too much. It runs on just about anything, and can be slimmed down far further than any other distro. I just can't justify businesswise the amount of labor it takes to maintain, when we are short on skilled *nix admins anyway.
Why can't I mod "-1 Idiot"?
Please reply that this was an elegant piss take, please
"Linux is for noobs"-The new MS fud strategy