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"
will wonders never cease? (Score:2, Funny)
The question is; why?
slackware has a new one, redhat, mandrake, suse, debian(shortly)... even the packages like mozilla and kde are having long awaited releases....
maybe we're about to stumble on the turning point on the computer era... maybe 10 years from now we'll look at the 1995-2002 as the dark ages of the operating systems.
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?"
Re:will wonders never cease? (Score:4, Funny)
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?"
Eight Point One is the Easiest Slackware Ever (Score:5, Funny)
"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!
Re:Eight Point One is the Easiest Slackware Ever (Score:2)
Now, my mother is working her way up to being a novice user. My favorite example is that I had to explain to her what to do when her mouse reached the end of the mouse pad, but the pointer hadn't reached its destination.
Say what you want about Linux's usability (for any distribution) vs. Windows or Mac, but I have no doubt I'd have been answering questions I can't even make up myself with any other platform. However, with Slackware I know that no matter what she does, I can fix it, and I have the best chance of being able to explain to her how to do things.
I think the experiment has paid off, since I haven't heard any problems from her in a long time now.
I wouldn't have dreamed of having her install her own OS - Windows or otherwise - but I think that the anecdotal evidence of her success is proof that pretty much anyone can use Linux, Slackware in particular.
I'm a slackware whore! too bad slackware.com sucks (Score:2, Insightful)
I've used 8.1-beta2 at work, I love it.
Re: too bad slackware.com sucks (Score:5, Interesting)
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.
One man show (Score:4, Insightful)
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.
Re:One man show (Score:1)
Re:One man show (Score:1)
Re:Best thing about slackware is the disksets (Score:2)
I've been looking forward to this... (Score:3, Interesting)
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!
Re:I've been looking forward to this... (Score:2)
This is exactly what I did with Slack 8.0 when it was new last year. Haven't looked back since. In fact, it's on all 3 of my systems now.
--Former Mandrake User
Why Slackware? (Score:5, Insightful)
I used to be a slack user... (Score:2, Interesting)
I don't use it anymore because all of my boxes (including my server) are running linux from scratch [linuxfromscratch.org] which while being much longer to setup (especially the first time), it is the ultimate learning experience. Everything on my workstation was compiled manually by me, including the shell, the compiler, X, etc...
One good thing about slack and linuxfromscratch is that you *know* exactly what is installed on your machine.
Re:I used to be a slack user... (Score:2, Interesting)
Recently I've switched to Gentoo Linux [gentoo.org]. It's the same no crap, basic distro that Slackware is with the added benefit of everything being compiled for your specific system and knowing exactly what goes on your system like LFS.
The reason I use Gentoo over LFS now is the package system (it's like BSD ports) is genius. I would recommend Gentoo to any Slack or LFS user.. you get all the benefits of the two plus an easier way of installing and uninstalling apps.
Re:Why Slackware? (Score:2)
Re:Why Slackware? (Score:2)
Re:Why Slackware? (Score:2)
I once ran an iptables script that had "set -x" in it over SSH. The script blocks all traffic while it's running, so the buffer ran out and it hung there waiting for the terminal... %-(
Luckily, the server was in the next room, so I just went in and re-ran the script from the console.
Re:Why Slackware? (Score:2)
Gentoo [gentoo.org]: the portage package management utility is based off the BSD ports system and downloads, compiles, and installs programs instead of using binaries for increased optimization. The only graphical configuration tools are the ones the user 'emerges' using the portage system. Much like Slackware and Linux from Scratch, you have complete control over your system.
Linux From Scratch [linuxfromscratch.org]: step-by-step instructions to compile your very own Linux from the ground up. Excellent docs that are worth a read even if you don't decide to install it.
Re:Why Slackware? (Score:2)
Re:You don't require Slackware to edit text files. (Score:2)
Exactly! And even after stating it you never understand it. Slackware does things in very standard ways, so instead of learning the peculiarities of a particular distribution, you just learn solid standard *nix.
The LSB is just wind. Slackware is the living standard that you can install on your machine, run, use, tinker with.
SysVinit is just annoying. RPM *shrug* you can install it on slack if you need it, knock yourself out.
Re:You don't require Slackware to edit text files. (Score:2)
No comment.
That's a troll? (Score:2)
Respond. Don't moderate me into oblivion. That isn't a troll. If you think it is, explain why.
Re:You don't require Slackware to edit text files. (Score:2)
Then again, I really think that Slackware is a good learning distro because it *forces* you to learn if you want it to work. If there's a lazy way to do something, I'll do it, so forcing me to learn is a good thing.
Re:You don't require Slackware to edit text files. (Score:2)
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:Already downloaded. It looks sweet. (Score:1)
Not dead - yet? (Score:1)
All that might be a good thing as the emergence of a clear commercial leader can only help Linux in the business world - it still looks like too much of an anarchy at the moment.
My first distro was a shrinkwrap job, but now I know I'd never do that again - there is no money to be made out of me or anyone like me. My contribution is in code and similar efforts.
When the shakeout comes then the hacker community are really going to be tested - without that money it is back to people in their bedrooms churning it out. Are they/we up to it?
Re:Not dead - yet? (Score:1)
Please don't bother flaming me about that statement of opinion, since that's all it is. I prefer the clean simplicity of slack, that's all.
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:Not dead - yet? (Score:4, Informative)
Um, last I heard, Slackware has always been profitable. Quit spreading FUD.
Re:Not dead - yet? (Score:1)
Oh man this is awesome! (Score:2)
Hooray for Patrick and gang! A job well done.
Re:Oh man this is awesome! (Score:2)
Slackware users since floppy days!
ttyl
Farrell
Will ESR join the Slackware team? (Score:1, Interesting)
Why I don't use Slackware anymore... (Score:2, Interesting)
I just don't have the time to spend a few hours grabbing the latest source patches and doing a recompile. I use to like to compile everything from source so that I could optimise it for my machine but real life eventually got in the way of that and it stopped being fun.
So for the past 3-4 years I've been using Mandrake. But the first thing I do is 'rpm -e linuxconf drakx* kde* gnome*' etc. The reason I like it is not because of the ease of use but because Mandrake is really quick to release security updates and all it takes is a simple urpmi command to download them. Plus every release comes with tons of new toys that I like to play around with when I'm bored.
There's lots of other reasons I choose Mandrake too but I mean this as constructive critisism towards Slackware so I'll leave those out.
Comming from a BSD background I always felt right at home with Slack but when you just want something that you can use and keep up to date and secure with minimum effort then it just doesn't cut it.
I don't feel that you need to be user friendly and geared towards windows and mac users to fill this gap. Just a few command line tools that make a UNIX administrator's life easier when it comes to managing what's installed on the system (and the pkg_* tools are not up to speed on this IMO).
So I'm going to go off on a limb here and get ready to be flamed by all the Slackware lovers. I would probably switch back to Slackware if they were to switch to rpm or deb pkg. They can keep the "no easy configuration tools" or the bsd-style init scripts which I love so much. But I really need a way to customize my system and keep it up to date with minimal effort.
I know Slack has come with rpm installed optionally for a while but all of the system stuff like glibc, bash etc. should be installed as rpms so that it's really easy to updgrade them without taking hours to recompile.
--
Garett
Re:Why I don't use Slackware anymore... (Score:2, Insightful)
I also have to say that in fact Slack IS the best way to learn about Linux (and BSDUnix) and whenever a friend wants to switch from windows to linux i tell him to use Slack. He probably has only heard about Redhat or SuSE but i believe using tools to do the job wont help much when further problems arise.
cu,
Lispy
Slackware has packages... (Score:5, Insightful)
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 [slackersguild.com] will always use Slackware... ;)
Re:Slackware has packages... (Score:2)
"Archaic" perhaps, .tgz is a basic standard that can be relied upon nonetheless, and more than adequate for most uses. What it lacks in fancy features it makes up for simplicity and reliability.
Or waiting a day or two until another slacker gets the source and generates a binary pkg against the current stable release. Between slackware.com and the various user sites like linuxmafia.com and linuxpackages.net most any needed software can be installed from packages, and there is a very high level of quality maintained in the compilation.
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.
If you like Slackware.... (Score:1)
Same here =) (Score:2)
But this doesnt mean i wouldnt use Slack if i need a system up and running fast, cause gentoo is still a slow bastard with all the nice compile time needed...
Re:If you like Slackware.... (Score:1)
Re:If you like Slackware.... (Score:2, Informative)
grr.... (Score:1)
Re:grr.... (Score:1)
Re:grr.... (Score:2)
Kudo's to Patrick and the team (Score:1)
I still have the CD for 3.2, from 1997
I've tried Red Hat and Debian, but I still come back to good old Hackware.
Roland
Re:Kudo's to Patrick and the team (Score:3)
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 [linuxfromscratch.org]. As someone pointed out before, Slackware is one of the best ways to truly learn Linux.
good news (Score:1)
Ciryon
ISO Mirror? (Score:1)
The mood of comment (Score:2, Insightful)
But what is more important - it still has users that loves slack.
Look at comments here! There are no angry posts. Almost everyone claims almost love to slackware, even users that had to go away from slackware. They were made to leave slack, but they still love it.
There are no post like BSD is dying, there are no troll or flamebaits commonly accompaning RedHat or Mandrake releases. Everyone seems to have warm feelings about Slack.
I think that slackware has one of best userbase around here.
Go slack!
Re:BSD is dying! (Score:2, Funny)
Even trolls think positively about slackware
no package managment? (Score:1)
Slackware rules baby! (Score:2, Funny)
Stupid RedHat and other GUI installs suck. If I wanted GUI I'd get a Mac.
I was there from the beginning. Slack is the best.
Give me Slack or give me Death!
slackware is the best newbie distro! (Score:1)
Re:slackware is the best newbie distro! (Score:4, Insightful)
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.
Slackware seems really up to date (Score:2, Interesting)
Slackware isn't anymore using old outdated software. Take a careful look in the changelog and drool.
Also note the boot/root disks supporting the new journaling filesystems directly from a fresh installation.
//Pingo
Great! (Score:2, Interesting)
Great this is good news!!! This is cause for a celebration!
More power to Slackers! (Score:2, Insightful)
Now troll on this if you can!
One Happy Slackware User, and Plenty Distro Wars (Score:5, Interesting)
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 [mailbox.net.uk] in my third job, and a complete domain registry [centralnic.com] 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:
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.
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: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.
Boot kernels (Score:2, Informative)
One Hell of a Change Log (Score:2, Interesting)
For the ones getting started ... (Score:2)
So in between official upgrade, take a loot at the linuxpackages.net [linuxpackages.net] site.
Re:Come on people (Score:2)
This from an ex-FreeBSD user that instinctively started with Gentoo, but who was very dissapointed; it is only superficially like FreeBSD (due to the ports system) but on closer look it is very diffent. Slackware truely remains the best choice if you're forced to run Linux (instead of FreeBSD), in my case because of lack of vmware-3 and decent Java in FreeBSD.
Re:Come on people (Score:2)
you can run linux jdk, but no hotspot variants (so no jdk 1.4 at this time).
still, if only i would have vmware-3 running well under freebsd i'd switch back in a minute.
Re:Come on people (Score:2)
Re:bah (Score:5, Insightful)
IT IS OUTDATED (Score:1)
You want outdated ? how about that tgz packaging system ? how much outdated can you get ?
Re:IT IS OUTDATED (Score:1)
Slackware is for people who enjoy compiling everything and optimizing it for their machine.
And it does it well. Slackware users don't want a packaging system for everyday use.
As far as time line, its a tad long, but again, slackware users stay on top of things and its not a big deal. Patrick never rushes releases. The result is a rock-solid base.
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:IT IS OUTDATED (Score:2)
Binary packages only. Src packages have too many problems. Theres an effort over at OpenBSD to audit all the ports tree due to the compile errors on a large percentage of the ports.
RPM is a damn good idea, but it falls short when you get hit with dependancy hell. On Solaris pkg is another good example, and a little easier to manage, and no compile problems.
Slackeware
Theres a time and place for source, and not everyone needs to compile for third party options, or try to milk 5% extra speed out of a program. A generic install base has advantages. I can setup a nat server with internal dns, port forwarding, and services in 20 minutes with packages. If I had to use src, it would take me much longer to compile everything. Slackware has been one truely small, efficent distro. I dont use it much anymore except when space is a premium. I'm using *.rpms mostly, so I use suse or mandrake for my workstations, I can get a computer up and running in minutes. Tweak time shouldnt take hours, even thou its enjoyable. (-;
-
for f in `ls -la *.rpm | awk '{print $9}'` ; do rpm -ivvh --force --nodeps $f ; done
Re:IT IS OUTDATED (Score:2)
Re:IT IS OUTDATED (Score:1)
Slackware gives us exactly what we want.
Re:IT IS OUTDATED (Score:2)
As I said in another comment, slackware users don't want a packaging system for every day use. We like to compile things, and tweak them for our own uses.
How about not speaking for all us Slack users, eh?
I have been using slack since '95 and while I do like the fact that I can compile things from source and not fuck up the system since there is no sense of dependencies, I prefer to create my own packages using checkinstall; I maintain about a dozen or so firewalls and when a security problem is identified I remake the package and push it out to all the systems. That way I have no need for compilers on all the systems.
So to conclude: this Slackware user wants a packaging system for day-to-day use. I compile+tweak once and push the new package to all the production servers.
Re:IT IS OUTDATED (Score:2)
Your a sysadmin not a user here
This is true. I run slack on my notebook too and I *definately* use source installs for things like KDE and so on, mostly because I don't want to wait for the package to be created.
Mind you now, once I've compiled here it's a simple matter of creating the package for any of my other machines. :-)
Re:IT IS OUTDATED (Score:1)
tar combines multiple files with paths into one file, and gzip compresses a single file.
zip is both of these features together.
(Tar came first as it was used to combine files into one to store on tapes, thus 'tar' which is 'tape archiver')
The extent of the slackware package system is that each
It also contains files to let the system know it was installed (for removals and sorta for dependencys, but just dependencys for removing files, not what you need to install)
The idea behind slack is only system software is installed from packages, which are on the CD.
You dont need packages for anything but the OS.
Anything YOU install (in
If you want a packaging system for non OS related software, use a distribution that has that, like almost any of the other ones have.
Re:dare to compare (Score:1)
Re:dare to compare (Score:2)
I started with Slackware in 0.98 kernel times (when was that, about 1992?). After one year I switched to FreeBSD, been using it since a few months ago as my main OS. Now back to Linux, my first try was Gentoo because of the ports system which should be FreeBSD like.
Unfortunately, while the ports system is nifty and interesting, I think Gentoo as a whole still very immature. Also it is really more a sysv-like linux, Slackware being the only linux that feels like FreeBSD (mainly due to the BSD-style simple init scripts). Also slackware packages are so easy to roll yourself.
The main problem with Gentoo, IMO, is that not only add-on software are packages (as is the case with FreeBSD, the base system being one big consistent piece) but everything. The result is that every user is running a configuration of ports making up the (basic) system that is quite unique, i.e. that is hardly tested. It depends on the time that you rsync the Gentoo ports tree. The 'locking-down' mechanism, which fixes certain versions of ports even when other (newer) versions are available can prevent this 'version hell', but in the current configuration it is not used enough. Many users complain on essential ports not being compilable or crashing, due to the fact that they have slightly different versions of other packages that have interactions.
I think that gentoo has potential, but at this time is no match for slackware. Also the quality of a distribution does not (only) depend on how nifty its package system is. What is more important is how well tested the system as a whole is, and (for me) especially how simple and understandable it is.
Re:bah (Score:3, Insightful)
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
Re:bah (Score:1)
If you're serious about learning Linux the way you should learn (by experience, not paper) it, slack is the way to go. It just goes to show why paper MCSEs and RHCEs are worthless... you gotta have experience before you get hired for a real job.
Re:bah (Score:1)
Slackware rocks (Score:1)
Re:wtf? (Score:1)
Sat May 25 12:38:52 PDT 2002
Well folks, we are now at Slackware 8.1-rc1.
Fri Apr 12 02:01:53 PDT 2002
We'll call this Slackware 8.1-beta2.
Who announces beta's/rc's like that?
He only really means it when he makes ISOs.
Re:What is Slackware? (Score:1, Informative)
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:gz vs. bz2 ?!?!? (Score:4, Informative)
Re:gz vs. bz2 ?!?!? (Score:1)
Re:Walnut Creek CD-ROM? (Score:3, Interesting)
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.
Re:slackware (Score:1)
And I say that as a slackware user.
Nice.
Re:gentoo (Score:2)
Lazy wimp. Go build your own distro. [linuxfromscratch.org]
In all seriousness, LFS is great when you've got a fast spare machine to play with and want to learn about how Linux works (I've got a "play box" just for this purpose), but I love Slackware for when I need absolute stability and resource efficiency. Good for desktops and servers, 486s to P4s. Thanks for the work, Patrick!
Re:gentoo (Score:1)
I learned most of the networking I know in the mid 90's by buying cheap 3C501 (yikes!) ethernet cards for $2.50 a pound at a surplus store and building three or four 386-SX boxes to run Slackware on.
That, and sweating through all the 'blue spine' O'Reilly books I could find.
Re:Boycott Finland (Score:2)
Re:Boycott Finland (Score:2, Funny)
You have been warned.
peace.
Re:Boycott Finland (Score:2)
Re:Userbase (Score:2)
Now the introductions are over, let's think about Netscape.
IMHO Netscape is bound to have more users than Slackware it runs on multi-platform, it is released with almost every Linux distribution.
Enough... you must be a troll?
Yet someone (a moderator) found this funny?
I just built a Dual Athlon system... I installed XP just waiting for 8.1 - no other Operating System will do, until 8.1 is avaiable.
PS Has anyone noticed this [bbc.co.uk] on the BBC? Is it a scoop or is it old news?
Re:Userbase (Score:2)
Re:Userbase (Score:2)
but having said that Slackware places an email in every root's inbox asking them to register for the Linux Counter Project, how many other distributions do that?
Looking at the numbers of the project I would say that their numbers are a huge underestimate.
Don't say that this is a smart marketing ploy by Slackware, they've been doing this for over 7 years. It's just a shame that other distributions don't do the same...
There are AFAIK two analyses of Slashdottings to the Linux couter project so I won't provide a Link