Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
GNU is Not Unix Linux

Slackware, Oldest Actively Maintained GNU/Linux Distribution, Turns 25 202

sombragris writes: Slackware, the oldest GNU/Linux distribution which is still actively maintained, turned 25 this week. The latest stable version, Slackware 14.2, was released two years ago, but the development version (-current) is updated on a fast pace. Today the development version offers kernel 4.14.55, gcc 8.1.1, glibc 2.27. mesa 18.1.4, xorg 1.20, and the Xfce and KDE desktop environments as default, with many more available as third-party packages. Other points of note are that Slackware is systemd-free, opting instead for a simple BSD-style init.

Since its first release ever, this has been a distro with a strong following due to its hallmarks of simplicity, speed, ease of maintenance and configuration. Happy birthday Slackware!
This discussion has been archived. No new comments can be posted.

Slackware, Oldest Actively Maintained GNU/Linux Distribution, Turns 25

Comments Filter:
  • by DogDude ( 805747 ) on Tuesday July 17, 2018 @12:47PM (#56963012)
    Slackware was my first (of many) attempts at using Linux, and it was less than successful. I love the fact that it's still going after such a (relatively) long time, compared to other OSS projects that often don't last very long. My question is: Is it usable yet? Is it worth trying again? Or, is it still only for super hardcore Unix people, only?
    • by Anonymous Coward

      For your first distribution I would not really recommend Slackware. It's better to use an easy distro first like Ubuntu, Mint, Fedora, etc.

    • by Anonymous Coward on Tuesday July 17, 2018 @12:53PM (#56963042)

      Yes it is usable. Yes it is worth trying again. Yes it is for people who use Unix.

      • And it's clean. When you type ls /etc (for example) it doesn't look like an unholy mess. You can figure it out.
    • by Schnapple ( 262314 ) <tomkiddNO@SPAMgmail.com> on Tuesday July 17, 2018 @01:05PM (#56963104) Homepage
      I'm no expert but this quote from Distrowatch has always stuck with me:

      There is a saying in the Linux community that if you learn Red Hat, you'll know Red Hat, but if you learn Slackware, you'll know Linux. This is particularly true today when many other Linux distributions keep developing heavily customised products to meet the needs of less technical Linux users.

      https://distrowatch.com/dwres.... [distrowatch.com]

      It seems to me that if you want to get into using Linux, use Ubuntu or Mint or something. If you want to get into Linux the hard way and really get your hands dirty then Slackware is up to the challenge.

      • Yeah this statement gets more complicated with systemd these days but I guess I'd still basically agree with this.
      • by junk ( 33527 ) on Tuesday July 17, 2018 @01:19PM (#56963200)

        Slackware was my second distro but the first (RedHat) was only on the box for a couple days before my really geeky friend shamed me into using Slackware. Soooooooooo painful. Soooooooooo hard to use. I was soooooooooo lost. I'm so much better off for it. I've been using Linux since the 90s and haven't ever stopped. I've run Slackware on laptops, desktops and servers for a lot of that time. I'm much lazier now and much more employed, so I use something with a native package management system that handles dependencies and laziness. When my home racks are online though, they're Slackware because it works, has always worked and will always work without any BS.

        Patrick and team have done a great job for a long time and they deserve a lot of thanks for their work.

        • Slackware was my second distro but the first (RedHat) was only on the box for a couple days before...

          LOL, #metoo

          My reason for bailing on Red Hat was different: I was on version 1.x of Red hat and the latest 2.x was out so I decided to upgrade. I downloaded all of the files, over a 14.4 modem no less. But, I couldn't upgrade because all of the packages were wrapped with a new RPM format... even the RPM utility itself. No way to use ANY of those packages without doing a fresh install... so instead, I went to Slackware and I am VERY glad that I did. Slackware kept the vision of being Unixy and of the user bei

      • by Anonymous Coward

        Or if you're a masochist, you learn on Gentoo.

        Confession: I learned on Gentoo... starting in 2005. I still maintain it was steep, but ... valuable.

      • As somebody who started with slackware, learned linux, and then switched to RedHat, I have to call bullshit on this one.

        If you already knew UNIX, all there was to "learning linux" for the average user was learning how to compile a kernel; back then it was often necessary in order to get all your hardware working. New USB device? You might need to compile the kernel again. And that was exactly the same on every distro. And then when the kernel's module system was more mature, and they could just ship all the

      • by novakyu ( 636495 ) <novakyu@novakyu.net> on Tuesday July 17, 2018 @03:39PM (#56964080) Homepage

        That's such bullshit. If you want to learn Linux, you use LFS [linuxfromscratch.org]. Anything else is for posers and babies.

        • My understanding is: LFS mean copy-paste-compile everyday, for hours. You need to repeat that cycle about 1000 times, maybe a few thousand times.

          Even if that does teach you something: I suspect there are more effective ways to learn UNIX/Linux.

          • by novakyu ( 636495 )

            Well, if your point is LFS isn't meant for a production system, sure, point taken (and to echo an AC sibling, if all you are doing is copy-and-paste, you are missing the point of using LFS, which is not to practice masochism).

            But if the primary purpose of choosing a distro is to learn how the operating system works (not just where a particular distro places its configuration files), then Slackware does not occupy the distinguished spot; it's just grouped with all the other distros with package management sy

        • LOL. That is such an absolutist way to look at it; although, it makes a great point. The wording should be diffrerent on the original claim. It should say something more like:

          Slackware will teach you more about being an admin for a Linux based system than the other distros will.

          Ultimately, you are correct that LFS will teach you more about Linux and at a MUCH deeper level. It does not really invalidate the original message though.

    • by jellomizer ( 103300 ) on Tuesday July 17, 2018 @01:07PM (#56963116)

      Slackware was my first distribution, but mostly because I didn't have any other options at the time.
      To answer your questions.
      Is it usable yet? It was always usable. It isn't a Desktop OS, but for a server system it has been really good, because it has such a small foot print.
      Is it worth trying again? I tired it out a few years ago, it is about the same. If you didn't like it then, you probably won't like it now.
      Or, is it still only for super hardcore Unix people, only? Slackware (Linux) and FreeBSD (Unix) are rather similar. However OS X is Unix, while Android is Linux. That said if your are a Traditional Unix guy, Slackware probably feels most comfortable. But if you are trying for a Desktop system then Probably not.

      • I just wanted to say that for software developers, slackware was always a perfectly good desktop OS. It is mainly non-developers who will feel the dependency/configuration pains. Software developers have to manage that shit anyways.

    • Re: (Score:2, Interesting)

      by Anonymous Coward

      Is it usable yet?

      Come on, dude. Do you really think it would still be here after 25 years if it wasn't usable? It was perfectly usable back when you tried it. The fact that you found it "unusable" tells us more about you than slackware.

      Slackware is simple, fast, stable, and has been used on production systems for a long, long time.

      • by q_e_t ( 5104099 ) on Tuesday July 17, 2018 @01:52PM (#56963376)
        Production systems very often use a commercially-supported distribution, as support is valued, or one of the open versions of those, as they tend to get patches pretty promptly. Whilst you could use Slackware on a production system, it wouldn't be my first choice from a risk perspective.
    • It was my first introduction to Linux as well back in '97 or so. It was definitely a learning curve but I was young and eager.... I believe I may have gotten Enlightenment running for a brief time but mostly, I was interested in the server-side stuff so didn't really bother with a GUI.

      Once Gentoo came out, I never looked back at Slackware and have long since ignored the milestone releases.

      Slackware is a point of nostalgia to me and not much more.

    • Well, look at this: I am a Windows user, and yet you know what distro I use when I want to do something in Linux that reminds me of a desktop and when I have free time for experimentation? Slackware. No kidding, Slackware.

      Why? In Slackware I can do whatever I want, in the way I judge best, without worrying about idiocies like those caused by GNOME, cyclical dependencies in half-assed package managers or now recently bizarre things like systemd.

      P.S: When I'm lazy or in a hurry I use Linux Mint
    • Slackware was my first distro too; I spent $5 on a lame magazine to get the bundled Slackware 3.0 CD. Everything in the magazine was mainstream stuff about windoze, but they did get a sale with that CD on the front.

      (Note: Magazines were a popular form of information distribution before broadband internet; they were like a snapshot of a website, printed out on expensive paper)

      It was great! I went open source and never looked back. I've run a few different linux distros over the years, and spent a few years o

      • Ah, the good ol' days. Slackware 3.0 was my first introduction to Linux, too, because, well, I didn't know any better. Got it up and running on a low-end Pentium back around '96. Got X11 installed on it and life was good. It didn't do everything I needed, but it did a lot. Even upgraded the kernel from v1.2.13 (I think) to 2.0.20 at some point, along with all the other stuff (gcc, glibc, etc.) needed to make that transition. Then 16 years later the system had basically become unusable for the modern w

    • Is it usable yet?

      It always was.

      Is it worth trying again? Or, is it still only for super hardcore Unix people, only?

      Give it a try. It might not be 100% easy to install (only 99% ;-) but it's very low maintenance. And for many people, believe me, this is a godsend.

    • Comment removed based on user account deletion
  • I like it. (Score:4, Insightful)

    by Qbertino ( 265505 ) <moiraNO@SPAMmodparlor.com> on Tuesday July 17, 2018 @12:57PM (#56963062)

    I considered moving to slackware during the height of the anti systemd ruckus, but went with Manjaro i3 instead. However, for a focus non-bloated Linux slack should a good choice, even if you have to keep a eye on your dependencies. ... I wouldn't want to install a full KDE setup on it though.

    Either way, distros like slack are very much needed in the distro ecosystem IMHO.

    • Slackware to me is the Traditional GNU/Linux. It is as close to a Pure Unix without being Unix.
      That said in 2018 is the need for the Traditional Unix as important as it was in the mid 1990's to late 1990's

      However a non-bloat distribution is good for more embedded systems, or semi-embedded such as appliances, where you have a PC doing a few things and doing it well. Slackware which you can setup on low resources is still useful.

  • by Glasswire ( 302197 ) on Tuesday July 17, 2018 @12:57PM (#56963068) Homepage

    Installed from about 6 x 3.5" floppies onto a 386SX system with less than a meg of memory. Needless to say, no X and no GUI :-)

    • by lgw ( 121541 )

      I installed on some ancient POS, probably 386. I remember 16 floppies for Slackware, and 32 for xwindows. Had to manually configure monitor settings (number of scan lines and timings) for the GUI. Good times.

    • It was not my first, but l eventually found Slackware through a man named "Wes" at the Tacoma Linux Users Group in 1996. Slackware was a few years old, but it got the job done! It really helped me get myself "under the hood" so to speak in a Linux distro. I still use it today and have Slackware 14.2 installed in my full tower PC, an old Dell Optiplex, and my laptop! I loved Slackware back then and still love it today! Happy Birthday Slackware and I wish you many, many, more too!
    • by thedarb ( 181754 )

      Oh man, I think the kernel was 0.99pl13, on my 386sx 16mhz. 2 meg of ram and a bunch of swap. Had to use the floating point emulation in the kernel. Took days to compile a kernel. Connected to the net over dial-up with a psuedo SLIP called Term or something. IRC II, via console terminal. Minicom and Kermit, zmodem... Ahh, the good ol' days.

    • Reminds me of what a friend from the local BBS told me in the electronic message he sent requesting hardware installation assistance: "I got MEGABYTES! MEGABYTES! Beer too, please help install"

      Yeah. magabytes: 2 of them.

  • by Anonymous Coward

    All 24 users gathered online to commiserate

  • Good old Slackware (Score:5, Interesting)

    by Nethead ( 1563 ) <joe@nethead.com> on Tuesday July 17, 2018 @01:16PM (#56963176) Homepage Journal

    I remember back in the mid 90's I hosted images.slashdot.org on a Slackware box (Pent 90, IIRC) because Rob Malda's T-1 circuit was getting constrained. I was working for the Seattle ISP Wolfe.net and we had a whopping T-3 with 45Mb/s direct to Sprint.

    Slashdot start off on Slackware.

    This, of course, was back in the dial-up days. Nothing like trying to find a ring-no-answer in a 400 line hunt-group.

    • by dsdhall ( 454643 )

      Slackware was the linux distribution I installed on a PC in the Wolfe.net office back in the day. 24 years ago, seems like a lifetime.

      P.S. Wolfe started with a 10M connection to Net99.

      P.P.S. It's still faster than my home connection today.

  • Slackware wasn't my first attempt at Linux, that was SLS version 1.0 (kernel 0.95), downloaded from a BBS onto floppies. But Slackware was the second-longest distro I used, way back in the day. Today I use Ubuntu, but only on a low-power web-surfing machine.

  • Good to see Slackware is still going, it was the first distro I installed. Nothing wrong with BSD style init, but I always thought Sys V style was better, and only a little more complicated. I've no idea what systemd is, as I stopped playing with computers long ago :)

  • It was my first, and I still use it for some things.
  • by toofast ( 20646 ) on Tuesday July 17, 2018 @01:29PM (#56963258)

    Like many, I cut my teeth on Slackware in 1995. There was just something about it -- even then, Windows sucked, OS/2 was cool but lacked the "tinker" factor and unix was unix. I would have never thought back then that Linux would become what it is today.

    Congrats Slackware, you've certainly helped many a generation of sysadmins and tinkerers along the way.

  • ...But when I did, it was slackware. I moved onto FreeBSD and then MacOS X after that, and now I'm not sure I really need a desktop computer at all anymore.

    Slackware was, counter-intuitively, the easiest Linux distro for me to use. I was already used to Unix systems from university, and slackware only gave you the stuff you asked for, not anything more than that. I always had trouble getting Redhat running, but Slackware did what I told it. I'm glad it's still around, just in case I ever decide I need a do-

  • Wow, you want to bring out the three and four digit uids just post a story about Slackware! :-)

    I still like it, though I haven't used it in the last couple of years.

    • by smed ( 252644 )
      Always good to see Patrick is still doing his thing ;) And I still have a Slackware file-server because...it's simple.
      25 years already? I'm definitely getting old.

      /off my lawn kiddies
  • Congratulations, Patrick Volkerding. You have made a linux user out of me, and a lot of others. (I recall being surprised that you replied to my question back then when I was attempting to install it on *gasp* a 486DX. Many moons later, and after printing out a bunch of HOWTOs, I am now a command-line penguinista, with a healthy disdain for candy colored icons on an even more horrid desktop. I'm looking at you, Ubuntu.

    As was mentioned above, ...if you install Slackware, you'll know Linux.

  • I have been using slackware for over a decade and its development version works fine for production purposes. It is updated frequently and uses a stable version of the linux kernel.
    noneya@noneya:~$ cat /etc/slackware-version
    Slackware 14.2+
    noneya@noneya:~$ uname -a
    Linux noneya.business.com 4.14.55 #1 SMP Wed Jul 11 19:33:43 CDT 2018 x86_64 AMD A6-3620 APU with Radeon(tm) HD Graphics AuthenticAMD GNU/Linux
    And now that you can easily update it with slackpkg its even easy to maintain. I highly recommend
    • its development version works fine for production purposes

      Well a slackware beta is generally more stable than other projects' LTS branch.

      No matter how many other distros I have tried over the years I always end up back at slackware. I find it doesn't get in my way and has far fewer issues with the software I run on it. For what ever reason GIS software builds wonderfully on it without issue yet has all sorts of problems that need tweaks on other systems.

    • Wow, that's impressive, business.com must be worth a fortune!

  • Recent releases from the "big boys" have gotten so bogged down with complexity that they're pretty much impossible to safely do updates to. You're often better off creating a partition for a brand new installation---especially if it's a major version update.

    I hadn't used Slackware since the days when the `Linux Unleashed' book was on the shelves at the local chain bookstore but after I wasted wa-a-ay more time that it should have taken trying to make Tumbleweed and systemd run a working firewall script--wh

  • I remember my first Linux install. It was Slackware ages ago on a 486 DX50. I stayed loyal to Slackware for a very long time. Perhaps it is time to take another look.
  • And now I feel old. Started using it in 95 or 96 and after failing for several days to download all those floppies I went and paid the $5 to get the CD from Walnut Creek CDROM and made floppies from that. Still own that CD and it sits in my cube window as my Geek Card.
  • My first free unix was FreeBSD in 1995, but it was not useful for my purposes, so I tried Slackware in 1996. I even bought "the book" (Slackware unleashed, i do not remember the version), mainly for the CD (In venezuela, BW was and still is scarce).

    Sadly, slackware and linux were also not fit for purpose (my thesis), so I moved past of Slackware to the greener pastures of RedHat and Suse. Nonetheless, I also learned HP-UX, Solaris, and Even Sinix, so I think my *nix is quite Ok.

    Nonetheless, I still have fon

  • My first experience with Linux was with Slackware in the mid 90s. I was in school, working after hours at a mom and pop dialup ISP in town, their equipment was a turn-key setup and the RADIUS server was a pre-installed Slackware box. One of the RAID controllers on it broke and I was the only one in the office who knew how to navigate at a bash command prompt. 19 year old kid on a conference call with engineers typing in Unix commands. Slackware didn't fail us!

  • I mostly like Slackware and have used it for many years. But 2 things eventually drove me away:

    1. Lack of binary packages for the add-ons at SlackBuilds.org. Building everything from source really makes no sense! Why not offer pre-built packages, at least for the popular architectures?
    2. Lack of any deadline whatsoever. When is the next version out? When it's ready! When will this version reach end of life? Who knows!

    Point 2 especially makes Slackware hard to take seriously (all the more in corporate environments

  • Seems just like yesterday. You really learned a lot about Linux without a package manager way back when.
  • by _hAZE_ ( 20054 )

    How many floppy disks does it take to install today?

    • How many floppy disks does it take to install today?

      Well, since a ISO image [slackware.nl] of Slackware-current amounts to 2.8 GB, i'd say that a full install of Slackware-current would take about 2000 1.44 MB 3.5" floppies.

  • ... was in college back in a computer science class' lab. I think it was in 1995/1996 for ANSI C programming.

  • by crispi ( 131688 ) on Tuesday July 17, 2018 @11:39PM (#56966252)

    Via a lot of compilation it's possible to update SLS 1.05 to the latest tools. I haven't the heart to delete /etc/motd. Big challenges were getting ELF going. getting libc6 going and cross compiling 64 bit from 32-bit. Now it's a 100% 64-bit system: /:softland:~$ cat /etc/motd

    Softlanding Software (604) 592-0188, gentle touch downs from DOS bailouts.
    Welcome to Linux SLS 1.05. Type "mesh" for a menu driven interface.
    Fresh installations should use "syssetup" to link the X servers, etc. /:softland:~$ uname -a
    Linux softland 4.16.14 #1 SMP PREEMPT Sun Jun 10 02:52:51 EST 2018 x86_64 unknown /:softland:~$ ld -v
    GNU ld (GNU Binutils) 2.30 /:softland:~$ gcc -v
    Using built-in specs.
    COLLECT_GCC=gcc
    COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/7.3.0/lto-wrapper
    Target: x86_64-pc-linux-gnu
    Configured with: ../configure --target=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --prefix=/usr --enable-languages=c,c++
    Thread model: posix
    gcc version 7.3.0 (GCC)

"Ninety percent of baseball is half mental." -- Yogi Berra

Working...