Slackware 8.1 rc1 Announced 297
Demerol writes with word that "about 12 hours ago, Patrick announced the that Slackware is now in Release Candidate stage in preparation for the long-awaited 8.1 release. Hundreds of updated to the current tree in the last few months have had all the slackers drooling, and now it is almost upon us. Now, I don't want to hear any more talk of Slackware being dead. Thanks. ;) Here is the ChangeLog
and the Userlocal announcement"
Already downloaded. It looks sweet. (Score:3, Informative)
Apache-1.3.24
php-4.2.1,
with all the php packages I have to move over,
MySQL-3.23.49,
LOTS of standard stuff (Nautilus, Mozilla etc.)
I should be able to upgrade my box, install ZendStudio_Server, use the journalling file system to mirror my drives and have the bullet proof system I need to support my Community Wikis.
Re:What is Slackware? (Score:1, Informative)
Re:Not dead - yet? (Score:4, Informative)
Um, last I heard, Slackware has always been profitable. Quit spreading FUD.
Re:IT IS OUTDATED (Score:3, Informative)
I agree entirely, but have one thing to add.
Slackware users don't want a packaging system for everyday use.
Try encap. [encap.org] Not really a traditional package manager, but works very well with source.
Basically, instead of "make install", you do "make prefix=/usr/local/encap/(programname-version) install", type "epkg /usr/local/encap/(program-version)", and it symlinks everything to the appropriate /usr/local locations automatically, deleting previous symlinks from old versions beforehand. Yes, you could do symlinks by hand, but that's a pain if the program uses a few hundred different files that can take too much time. Epkg does it in a few seconds.
New version of, say, your favourite email client is misbehaving? "epkg -r /usr/local/encap/(programname-version)" deletes the symlinks. Easy as pie. I love the encap concept since I try lots of bleeding-edge CVS versions of programs. If a new version sucks, I can go back to an older, working version with just a few commands. I don't have to recompile old versions over again.
Re:gz vs. bz2 ?!?!? (Score:5, Informative)
Patrick won't use bzip2 because it's too resource-hungry for the very low-end that slackware still supports, and also he claims that the difference at gzip -9 vs bzip2 -9 isn't enough to make it worthwhile anyway.
Re:Not dead - yet? (Score:3, Informative)
I'm immensely proud of my association with Slackware and with Patrick, but credit where it's due and all that.
--Logan
Re:Why I don't use Slackware anymore... (Score:3, Informative)
Having switched from an RPM-based distro (Red Hat) to Slackware, I can honestly say that I don't miss RPMs at all and like having the option of using either source or Slackware packages, which I can actually use together properly...without dependency hell.
Re:gz vs. bz2 ?!?!? (Score:4, Informative)
Why I use Slackware (Score:5, Informative)
The lack of "forced" package dependencies is a good thing. When I know exactly what I want, I don't need to care about "forced" package dependencies. I run a Debian laptop at home, and when package dependencies break (ok so I'm trying out the unstable branch), it can be a real pain to fix that back. And I don't even want to get started on RPM (yes I run a Red Hat box too). But if I know exactly what I want, I can fix everything myself in Slackware. I'm not forced to accept what a package/distro maintainer wants me to install. It's all about control.
Learning Linux/UNIX. Some of you have already mentioned this. If you really want to learn about Linux/UNIX administration/development, Slackware is a great distro for that purpose. Now, people who would just want to use Linux as a desktop (for non-programming purposes) should use another distro. Slack's not for you. However, people who really want to learn will love the DIY-ness of Slackware. When you have to compile stuff yourself, or figure out why a certain library isn't working, you'll learn a whole heap of skills and tricks that will be really useful to you later. For example...
Moving back and forth from/to BSD is a breeze. When I first had to admin an OpenBSD box, I felt right at home. The similar *.tgz-style packages were easy to admin, and so was editing/configuring the system via editing text files. I later had to do some research using FreeBSD boxes, and again, I'm on familiar ground.
There are a whole lot of other reasons too, but I can't spell it out right now due to my current semi-hangover mode...
The downside: Of course, the obvious downside to using Slackware is time. You need to have heaps of time to learn and use it. But once you're done with that phase, you'll find your investment in Slackware will be worth it all. Again, I stress that Slackware is not for everyone. I certainly don't expect some of my less-obsessed-with-UNIX friends to like it. But hey, if you're the adventurous type who loves to learn and tinker around with stuff, go try it out. I think you'll like it.
Re:If you like Slackware.... (Score:2, Informative)
Boot kernels (Score:2, Informative)
Re:Why I use Slackware (Score:3, Informative)
I agree with you totally on the dependencies thing. That's the main reason I installed Slack about a year ago. I bought the Mandrake 8.0 Power Pack for something like $80, discovered it was crap, and downloaded Slackware 8.0. It's on all 3 of my machines now and I haven't looked back.
The downside: Of course, the obvious downside to using Slackware is time. You need to have heaps of time to learn and use it.
I think I disagree with this. The time spent on learning Slackware is time that you'll spend on learning Linux itself anyway. If you're coming from one of the Bells-and-Whistles distros (like RH, Mandrake, or Suse) then you'll actually save quite a bit of time because you aren't trapseing all over the whole system disabling things, getting rid of performance wasters, and closing security holes.
I'll bet I could customize a brand new Slackware install to my tastes within an hour. Doing the same with Mandrake (for example), used to take me upward of 2 or 3 entire evenings.