Slashdot Mirror


Slackware 9 Unleashed to World

kiltedtaco writes "Slackware Linux 9.0 is out! Based on gcc 3.2, and equipped with kernel 2.4.20 (ptrace-patched), XFree86 4.3, GNOME 2.2 and KDE 3.1. You can read the full announcement, or just go grab a copy for yourself at either the Slackware Store or these lovely mirrors." I know a lot of people who first cut their teeth on Slack when trying Linux. It's cool to see that it's still around.

14 of 349 comments (clear)

  1. First useful post? by BRTB · · Score: 5, Informative

    Since the official Slack FTP is a bit slow from everyone trying to grab it, here are a couple (unofficial) mirror lists:

    alphageek.dyndns.org
    AbnormalPenguin.com

    I've already downloaded mine, so everybody have at it. ;)

  2. Re:I love Slack! by phreaknb · · Score: 3, Informative

    autoslack - written by David Cantrell

  3. Re: fp by ThePurpleBuffalo · · Score: 4, Informative
    I'd just like to point out that user "volkerdi" is Patrick Volkerding - the head Slackware guy.

    Personally, I laughed out loud when I saw this post.

    I think it's unfortunate that Mr. Volkerding, who has worked very hard for MANY years to help Linux, is rarely recognized.

    Or maybe it just seems that way...

    Beware TPB

  4. Re:What's so special about Slackware? by forged · · Score: 2, Informative
    Slack is the distro for those who want to learn. I was a total newbie when they unleashed SLS on me in '94 (SLS was the precursor to Slackware). SLS and Slackware were the two only distros where I really learned the stuff.

    So in a sense, yes Slackware is for the newbie, but no it won't hold your hand: you have to walk the path yourself.

  5. ISO image available anywhere yet? by Lawrence_Bird · · Score: 2, Informative

    In fact the 9.0 was on mirrors last nite, but the only ISO image was for 8.1

  6. Re:What's so special about Slackware? by Rooktoven · · Score: 3, Informative

    Au contraire.

    I've found that it is much more forgiving in the way of dependencies than RPM based systems-- in other words, you can install slack-packages and ./configure && make install other software without getting trapped in dependency hell. The only time I have ever encountered any library issues is when riding on the bleeding edge of slack current, and even then all the essential networking tools have remained rock-solid.

    At my company we're moving our mix of Suse and Red Hat servers to all slackware, and I for one couldn't be more overjoyed. (But then I'm lazy and like to just installpkg *, read my fortune and get on with life.)

    --

    Acquiescence leads to obliteration
  7. Re:What's so special about Slackware? by Anonymous Coward · · Score: 5, Informative
    its complete lack of package managment,

    It does have package management: installpkg, removepkg, and upgradepkg. It is far, far superior to RPM-based hell. RPM breaks the golden rule of programming (KISS) with a giant sledgehammer; just look at rpm --help, which I won't list here, as it's 154 lines of help options. That's just inexcusable.

    The beauty of slackware's package management is that is doesn't check for dependencies. At first that might seem like a bad idea, but for power users (which is Slackware's target) that is best. What if I've upgraded a package manually, by installing from source (or really any way besides installpkg/upgradepkg)? For Redhat, you've got to fight rpm because it really doesn't like to install without all the dependencies listed in its rpm database. On Slackware there is no problem at all.

    Additionally, RPM files suck. How do you get the files out of the package, if you just want to see the files and don't want to install? Use alien to convert it to Slackware tgz format.

    And how do you see what files each package includes? For rpm, you've got to use rpm to "query" the binary database. Uck. Not very powerful. However for Slackware, all the files are listed in text files in /var/log/packages/, each file representing a package. You can use any of the many powerful file and text processing tools that come with all GNU systems, for example to see what packages put files into /sbin, just do "grep ^sbin /var/log/packages/*" - now that's powerful! And to find what files are in a Slackware .tgz package, just do "tar ztvf package.tgz".

  8. Slackware - a sharp tools distro by spaceyhackerlady · · Score: 4, Informative

    My first "real" computer was a 486/66. I bought it used, and it came with Windows 3.1 on it. After firing it up and marvelling that people actually paid money for such a piece of crap, I went to the local bookstore and came home with a book that included a Slackware CD. Dunno what distro, but it would have been an old one (3.0?). I've run Slackware ever since.

    I had no difficulty getting the thing going, PPP, sound (an excellent excuse for boning up on DSP!), the works. It ran fine in 8 MB RAM. OK, except for Netscape, which page-thrashed for about 2 minutes then ran fine. Upgrading to 32 MB (the capacity of the motherboard) cured that. Now I run a Pentium 3 with 768 MB RAM, plugged in to ADSL. The OS started as Slackware 8.0, but I've upgraded many packages, and run a 2.4.20 kernel. It flies...

    To this day I recommend Slackware as a "sharp tools" distro - if you know what you're doing, it's immensely powerful and flexible. If you don't know what you're doing, you're screwed.

    FWIW, my most recent Slackware install was Slackware 8.0 on a Toshiba laptop that RedHat 7.3 (the company standard) refused to install on. It would get to about 3 packages before the end, crash, reboot, say GRUB and sit there staring at me. The PCMCIA network card did all the right things, automagically. I had to fiddle a bit with the X configuration to set up yet another weird-ass laptop video card. Big deal.

    Thanks, Patrick. Well done!

    ...laura

  9. Re:Too much crud by slugo3 · · Score: 2, Informative

    Except for Samba, PoPToP,

    1. Slack has Samba included in the N disk set weather you choose to install it or not is up to you.

    2, Slack uses Popa3d by default but your welcome to chang it to whatever you like.

  10. Slackware Linux Essentials by Alan+Hicks · · Score: 5, Informative

    You'll notice at the slackware store that there is a wonderful paperback book licensed under the GPL entitles, "Slackware Linux Essentials". It is perhaps one of the best linux books I have ever read and am thankful to be involved with.

    Mysel and many of the "BOZOs" in alt.os.linux.slackware are currently working on a revised edition to bring this book up to date with the latest release of Slackware Linux. You can take a look at our (so far meager) progress here. I encourage anyone who wants to participate to give me an e-mail, you can find my address at that link, as well as a mailing list for this project. Any contributions would be greatly appreciated.

    Slack on!

    --
    Slackware, what else when it must be secure, stable, and easy?
  11. Slackware 9 ISO url by punkmac · · Score: 2, Informative

    http://media.punkmac.com/slackware-9.0-iso/

    since its still hard to find at the moment, figured i'd toss it up. check those md5's as normal.

    enjoy

  12. Re:Enlightenment... by Skweetis · · Score: 2, Informative
    Hmm...

    # mount -t iso9660 /dev/cdrom /cdrom
    # ls /cdrom/PACKAGES/enlightenment*
    enlightenment-0.16.1-i386.tgz
    #

    I found it in my copy...
  13. Re:Not easy to install? by Accipiter · · Score: 2, Informative

    What I REALLY want is, a way to upgrade from version n to version n+1 without reinstalling from scratch. It is saddening that no easy way to do it exists,

    Slackware has had an easy-upgrade capability since 8.0. I upgraded from 7.1 to 8 with absolutely no problems. And it was easy.

    Check this out - easy upgrade instructions. While it's not as simple as "apt-get upgrade", it's hardly a nightmare. Give it a shot.

    --

    -- Give him Head? Be a Beacon?
    (If you can't figure out how to E-Mail me, Don't. :P)

  14. Good for older systems too by cascadefx · · Score: 2, Informative
    I know a lot of people who first cut their teeth on Slack when trying Linux. It's cool to see that it's still around.


    Still around?!?!

    Of course it is still around and it is really good. I use it for older or "non-standard" systems that other distros won't install on without a lot of hand-holding and research into why the next newest and greatest graphical installer for distro X keeps hanging.

    Two things that are great about Slack. First, it doesn't assume much about a system, but at the same time holds your hand enough that you don't have to know the scan rates (et al) or other specs your hardware intimately unlike *cough*debian*cough* (though I really like debian). Second, it fails gracefully. If something doesn't launch or was scanned improperly (or whatever) Slack will try to bring it up. If it can't, it throws and error exception, and continues about its way as best it can. I HATE when many systems just hang on installs. THAT is the WORST behavior. Graceful failure is an art and Slackware is very good with its paint brushes.

    Case in point. Work gave us these crappy IBM laptops that actually are ACER low-enders. I love IBM and hoped for a better model, but we got these. Having a dual-boot situation of 2000 and Linux woud be really helpful for the types of problems these laptops were meant to help us troubleshoot, but getting SuSE (one of my favorites), RedHat, or Debian to load was a nightmare... mainly due to the USB configuration (it uses an internal hub architecture to split the USB ports... or something... whatever, Linux doesn't like it) among other things. Slackware (the distro that I cut my teeth on, Slackware 96 from Walnut Creek) was mentioned as a possible route. After grabbing the CDs, It installed (with a much easier to use installer than I remember) without one hitch. I love it.

    So... give it a try. It is stable, it looks a lot like System V Unix and it is a great little OS.