Slashdot Mirror
Slackware 8.1 rc1 Announced
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"
Have you looked at the package list? It is one of the most up-to-date Linux distributions in fact; just look at the package versions and compare to any other Linux distribution. All this coming from one man, and offering the most stable and understandable Linux distribution is truely amazing.
You can check your email and receive messages from the world wide web! Slackware will help you stay in touch with all your friends by making a buddy list. I know that I instant message my friends all the time. Plus the new Slackware comes with bright shiny buttons, surprising sounds that make you excited about the interweb and being in-touch with folks from around the world who are just like you!!!!!
"Slackware's tech support has been nothing but patient, understanding and helpful!" says grandmother Eunice Haversham.
"It's so easy even I can use it!" says Michigan resident Robert Malda.
The best thing of all about Slackware is the fact that it's FREE !!! Just pick up a copy at McDonalds in their Tux Happy Meal or download it from your favorite website or give us a call at 1-800-LUNIX4U right away and we'll tell you about our other great offers!
It's simple, quick, has a decent interface for installing (non-graphical, non-slow) and once you get it up and running, it is running. It was one of the few distrubutions left where you can get it up, upgrade the kernel to whatever the hell you want and it will [b]still[/b] run. It knows it's target group and delivers.
Packages are good, decently up to date (now) and are not overkill. I couldn't be more pleased
What really amazes me about slackware is that it really does seem to be a one-man show.
This is reassuring to me. It's good to know that there really is one authoritative voice on at leat one distro.
It lacks bells and whistles and requires some expertise, which is why I couldn't stick with it, but philosophically, it appeals to me.
evanchik.net
I was going to download Slack so I could install the base and just do the ./config, make, make install dance for a buncha stuff I like to use, like evilwm. My intentions was to pull something together from installing just the bare libs and packages I need, and create a desktop box for myself that just plain works.
Slackware may not be for everyone, but that doesn't make their efforts any less relevant. They're a proven distro. Looking forward to this!
spam, spam, spam, spam, e-mail, news and spam.
Some people may be wondering why someone would use slackware when there are distros like Mandrake which have a graphical configuration utility for everything. There is a very good reason: to learn about Operating Systems and about Linux. To change a configuration in Slackware, you have to edit text files. But that's not really bad, because Slackware has amazing comments in the config files. You are encouraged to learn the filesystem and the config file structure. If you want to learn Linux as opposed to simply use Linux, run Slackware!
A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
Latest's of every thing I need:
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.
MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
They were acquired by BSDI, because of their support for FreeBSD. Then BSDI was acquired by Wind River Software, entirely for BSD/OS. Pretty much everything associated with them is dead now, AFAIK. Well, FreeBSD has survived, because its development was never dependent on commercial support. And slackware has been hurt by the loss of all of its paid developers, but its always just pretty much been Pat's distribution and despite the lack of support 8.1 looks to be coming along very nicely.
"(Man) tries to live his own life as if he were telling a story. But you have to choose: live or tell." --Sartre
The Linux distro business model just doesn't work...
Um, last I heard, Slackware has always been profitable. Quit spreading FUD.
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
-
...and now she's ready to learn.
Somebody mod that girlfriend up!As a side note, I showed my girlfriend the article about sherwin williams, and she replied, "this linux thing isn't going away, is it?"
I agree entirely, but have one thing to add.
Slackware users don't want a packaging system for everyday use.
Try encap. 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.
This is a slackware FAQ.
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.
I'm immensely proud of my association with Slackware and with Patrick, but credit where it's due and all that.
--Logan
Oh, please. As you know, Slackware has its own package management system, the same one it uses to install with. glibc, bash, and so forth *are* installed via binary packages. No need to recompile. Just follow slackware-current.
I upgraded KDE 2.2.1 to KDE 3.0.1 just by downloading the packages and using upgradepkg. I've also upgraded the kernel, a bunch of my X apps, and even X itself. All without compiling.
I should probably point this out--I'm an idiot. I probably shouldn't even be using a Linux system. But someone like me got Slackware Linux up and running and using all my devices. Wasn't hard at all. And now I have no reason to use Windows except to run certain games.
Then again, maybe I'm just ignorant since I haven't used any other distros since I first used Slackware 4.0. I guess I don't need to try the others when I've already got the best. :)
(shameless plug) Slackersguild will always use Slackware... ;)
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.
I'll say this. Because of Slackware's "raw" way of doing things, Linux isn't really as intimidating as it once was when I was but a newbie. Redhat's RPMs were nice, but I always wondered where everything was going, what it was doing behind the scenes, etc.
Having used Slack, that mystique is gone, and I'm okay now with the basic internals of Linux. I just grew comfortable with it since Slackware exposes it all. Hell, I'm even toying with doing Linux from scratch. As someone pointed out before, Slackware is one of the best ways to truly learn Linux.
The main disadvantage of bzip2 is that it's MUCH slower than gzip.
They that quote Benjamin Franklin on liberty and safety deserve neither.
I'm a happy Slackware user. I've been a Slack user for years - and not just out of "being used to it". I used Slackware in my first job, I built mailservers on it in my second job, I used it to run a complete ISP in my third job, and a complete domain registry in my fourth job (incidentally, I'm still on a heck of a salary and really enjoy my work).
I've actually looked at other distributions to make maintainence easier, but:
- Debian I found was populated by anal freaks who were real religious fanatics - we had a department full of Debian people and I said "ok, let's do Debian then" and two years later I'm finding it hard to work out just where they put everything [1].
- RedHat just had too many problems and decided to SetUID root a load of crap (plus there's the obvious rootkits).
- SuSE fell apart at the seams.
So I went back to Slackware.It's quite funny when someone came along, found a security hole such as the recent OpenSSH hole, and tried to crack a Slack box - it was fairly obvious from the start, because the rootkits failed. Then I built Slack packages for tripwire and stuff.
Pat's got it right, IMHO. It's a good, simple distro with decent ground-up building. And there's a lot of misconception that you have to build stuff on Slack boxes - you don't - you can quite happily build packages.
I now run Slack on my laptop, on the company servers, on my desktop, and loads of other places. It works for me. I'm pleased to see Pat's finally got it together for 8.1 (I've been following the updates for some time).
But one bit of advice: update slackware.com - it's bloody old.
Snogs,
Joel.
[1] Admittedly I haven't got used to it in the same way I got used to Slack, but there's enough people in the company who can get used to Slack. Standardising means getting other people to learn it too.
Smegma.
alt.os.linux.slackware has known that rc1 on was out for a few days now and someone on the group even makes the effort to make current ISOs on a weekly bases. Other innovations mentioned in that group are the ability's to easily install slackware from ftp or DOS.
Ascii artist &
I've been using Slackware since 3.5 back in 1997, and I continue using it today. In fact, I'm posting this from my Slackware 8-ish box. So why Slackware? It's all about simplicity. Let's get more specific...
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.
Actually, when I first installed Linux in 1998 i considered lots of distros (Debian, Caldera, RH, Slackware, and probably some more). Finally I installed Slackware because that was the only distribution that had an installation procedure that felt... solid (and worked from floppies). I had never used Linux, and had only little experience of Solaris from University. In a month I had Slackware 3.6 running on a Compaq LTE 5300 laptop. The PCMCIA modem worked. The TFT-display worked. I downloaded tarballs and recompiled my kernel.
I dont think I would have made it with another distribution. Whats so good with Slackware is that if something does not work, then you know it is your fault. There is always something you have done wrong, or something you dont know or understand. I'm a pretty experience Windows user, and when things dont work in Windows, its always Windows fault (Its true!). Its never slackwares' fault! I find it much more reassuring to know that solving a problem is just a matter of gaining more insight into it, not a matter of luck. It is always possible to understand what is wrong when using Slackware.
Nowadays I use OS X for daily work, and Debian for other needs (unfortunately OS X can do most things I ever wanted with Linux. so I hardly need Linux).
If I wanted a Linux desktop today chances are I would finally give Suse, Mandrake or Redhat a chance - they seem to be pretty good nowadays.
If I was to set up a server I would stick to Slackware or Debian.
If I wanted to learn or explore I would try Solaris/x86 or BSD, preferably on some odd hardware...
So what did I want to say? Hmm. Start with Slackware, dont give up - there is always a solution (and it is a great feeling to solve problems by really understanding them). When you know Slackware you can use any other Linux-distro you want - if it suits a particular need well. After running slackware you also have a good feeling of what UNIX is, and you feel like you basically can use any BSD or UNIX system.