Slashdot Mirror
Slackware, Oldest Actively Maintained GNU/Linux Distribution, Turns 25
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!
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!
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?
I don't respond to AC's.
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.
We suffer more in our imagination than in reality. - Seneca
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 :-)
Seriously, why does Slashdot tolerate this spam? Trolls have decided to harass a user, creimer, and continue to post spam comments about him even though he apparently doesn't post here any longer. It contributes nothing of value, isn't really even trolling, and gets posted in multiple threads in story after story. Given that it often references people by name, this content is actually defamatory in nature. Surely Slashdot can do something more to combat this persistent spam. Moderation just isn't preventing it from being posted repeatedly.
Slackware introduced Pulseaudio recently, and if I'm going to run Linux at all, it'll be Poettering-free. So far they've rejected systemd at least, but I don't think they can hold out much longer on that front, since all the major desktop environments have been co-opted by now.
Just curious why it's been two years since the last release.
All 24 users gathered online to commiserate
Linux has support for newer drivers for more hardware. BSD works or doesn't work. Sometimes you are better off with a buggy driver then not being able to use the hardware.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Cue systemd hating crowd blah blah slackware is the best, no "shitstemd", the unix way, tradition, "stupid package managers and who needs them", "it's like BSD but it's not BSD and I have no clue why I'm not running BSD if I admire it so much", etc....
Savvy?
I wouldn't want some monolithic daemon infecting my system even if it was GOOD, but the systemd virus sucks. It isn't good at a single aspect of what it has sucked in.
-- http://anonet.org -- The internet the way it was meant to be. Check it out, you may be surprised.
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.
-- I have a private email server in my basement.
It's only fair that it be celebrated, considering how popular Slack seems to have become recently.
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.
Boobies never hurt anyone. - Sherry Glaser.
You must be one of those types who enjoys a good daily flogging by your master.
Comment removed based on user account deletion
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.
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.
Slackware on 3.5" diskettes were my first install of Linux. It went onto an oldish 486 with 4 meg of RAM. I did it because I had read that because of the way it was licensed Linux couldn't be bought by Microsoft. After getting things running I had a look at the command line and did a bit more reading. My first impression was "this is like DOS ... on steroids .. for adults, ooh look at all the toys ... whee".
...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-everything server-ish machine again.
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.
This is not an illusion, a rip-off, or a ninja technique!
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.
WARNING: Smartphones have side effects--most of them undocumented.
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. /etc/slackware-version
noneya@noneya:~$ cat
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 using it because of its lack of cruft. You can identify everything in the process list which is really nice compared to things like redhat.
Long live slackware
Comment removed based on user account deletion
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--which had dutifully been doing it job on a truly geriatric version of Red Hat (on hardware that I was fearful would soon fail)--I finally threw my hands and decided to give Slackware a try. Now I haven't used it since the mid-90s but was pretty impressed that, after a fresh install of Slackware, tweaking a couple of files in /etc/rc,d, and rebooting, I had the firewall back up and running. Elapsed time: just over an hour---and a good 25% of that was waiting for the md device to finish initializing. There's a lot to be said for keeping things simple. I can add any necessary complexity if I need it. So many other distributions insist on it right out of the box.
CUR ALLOC 20195.....5804M
Comment removed based on user account deletion
And yet, you tolerate the monolithic kernel.
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.
Brought to you by Carl's Junior.
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.
Time to offend someone
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 fond memories of Slackware, and get very happy when I hear news about them.
A toast to patrick for the 25 years of his project, and a pint for his tenacity to overcome the obstacles (financial, health and others) to keep it running.
Here is for 25 moreyears!!!
*** Suerte a todos y Feliz dia!
Oxymoron spotted. "Kernal"b = look it up. The central, essence, core part of something. I don't mind say, a scheduler or a driver or an app being "monolithic" as they do...one thing and do it well. Systemd on the other hand -tries to do everything and does most of it poorly. Further it breaks some things such that if say, something is mounted remote but can't be unmounted due to a bad connection or the thing being down, it takes many minutes to remotely reboot - if at all. So if your machine is in a place you have to drive to - or crawl through a tunnel to, or be exposed to radiation in, you got trouble right here in system city.
Why guess when you can know? Measure!
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!
Have you been on a system with a micro kernel?
You still don't know that systemd is modular? Do you even understand the difference between a compilation unit, and a binary distro package? Doesn't your distro also include source packages?
Me, if I had whiny complaints about software I'd at least want to understand the basic vocabulary so as not to be a complete ass, but obviously YMMV.
I will say that I'm glad that systemd works fine with SysV init scripts, because I wouldn't want to rewrite the ones I already have, but that said, I sure as fuck wouldn't want to be stuck writing new ones when there is an option.
Do you know why distro maintainers don't split systemd's compilation units into different distro packages? Because none of the whiners even have a use case. It turns out, 100% of their problems are based on being aliterate and not reading the friendly manual.
And if you don't know what aliterate means, please post a reply telling me I spelled illiterate wrong, I could use a good belly-laugh.
Comment removed based on user account deletion
I mostly like Slackware and have used it for many years. But 2 things eventually drove me away:
Point 2 especially makes Slackware hard to take seriously (all the more in corporate environments). The name doesn't help either!
Knowledge is power; knowledge shared is power lost.
no habla. go back to mexico.
I have a warm fuzzy spot in my heart for Slackware. Installed it on a 486/33 :-) Brings back memories. *Sniff* Using Linux still to this day, but got lazy. Mint is just fine for most user cases so it is my current goto... but I can install any distro and and OS thanks to what I learned back in the day! Thanks Patrick (and Linus).
Slack is the gateway drug to BSD. Just sayin!
Comment removed based on user account deletion
Seems just like yesterday. You really learned a lot about Linux without a package manager way back when.
Fuck Ajit Pai
You still don't know that systemd is modular?
Speaking of belly-laughs...
Modular software requires well defined interfaces that separate abstraction from implementation.
A good anti-example is DBus, a "module" that most of systemd cannot live without.
Go ahead, try to write something compatible with DBus without looking at that list of "D-Bus secret internal implementation details".
Modular ... You keep using that word. I do not think it means what you think it means.
How many floppy disks does it take to install today?
Don Head
UNIX/Linux Administrator
Alliteracy is becoming quite common.
I was working at a lab that used a lot of unix. I learned about linux from a colleague there, installed slackware on my system. I could not get my system to connect to the LAN, so my friend said "hey, this is open source". He opened up the source code file for the network driver code using a text editor, found that we had to configure the code to use the BNC connector on the read of the 3COM 3C509B combo network card, then recompile the driver, then load the network driver module into the kernel, and voila, my machine was online. That was pretty amazing.
After using slackware for a while I switched to Red Hat, I got in on the red hat stock IPO because of beta testing and bug reports I filed, then switched to fedora when redhat went commercial, and then I was a beta tester for ubuntu warty warty warthog (debian, python, and gnome) before the release in 2004. Been using ubuntu since 2004, I have some professional engineering software that works well on ubuntu and it is is supported and approved at my place of work. Of course I occasionally try out various linux offerings in virtual machines but pretty much stick with ubuntu these days.
prsdntl
Alliteracy is gradually gaining greater global gravity.
"Slow down, Cowboy! It has been 3 years, 7 months and 26 days since you last successfully posted a comment."
Yes stupid posts like this, and others are posted in every discussion, but they are quickly moderated down to -1, hence becoming hidden with default settings, and thus mostly harmless.
Slashdot has long operated on the policy that it only deletes posts in very limiting circumstances, like they a court order or valid take down request. Other than that all moderation happens in the open. Any user can see all the posts by setting their viewing thresholds to -1, allowing them to notice abuse in the moderation system and correct it. People who don't want to see all the garbage can leave their settings at the default. This transparency is a wonderful feature of slashdot, one that I would really hate to see changed.
In addition to being systemd free, it still comes with SeaMonkey. And I haven't noticed any dependency problems with pkgtool and slackbuilds
“He’s not deformed, he’s just drunk!”
... was in college back in a computer science class' lab. I think it was in 1995/1996 for ANSI C programming.
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
I'm not so sure that this isn't cre'mer doing it himself. I've been using all my spare mod points on him ever since he suggested that instead of being "jealous" of all the money he's making with his spam, we all start spamming Slashdot ourselves and bask in the "long tail revenue streams".
I've also made a number of suggestions intended to get him to improve himself or see that he can't spam Slashdot and expect to be welcomed here with open arms. I think it's fine to spam the guy's comments and modbomb him into oblivion but Randomly spamming Slashdot comments with shit about cre'mer is just as bad it defeats the whole purpose of containing him. Does anyone really want to see more of his posts? No of course not.
FCLM if it's you. You'll just drive me and other users away from the site. I can't know for sure but I'm probably one of your most ardent supporters in your quest against cre'mer. We need to educate the users why he's so bad , report his affiliate program violations to the services he uses, and coordinate to use our mod points.
The reason I find him so offensive is that this is a classic site and one of the few where I can enjoy have old internet style intelligent discussions with a small group of actual nerds. We can troll, we can chuckle but the site gets maybe 1000 posts a day so it simply cannot survive a bunch of people making offtopic shitposts all over main discussion threads no matter who it is.
It is a simple and very fast distribution. It shows what Linux is really capable of without all the overhead of SELinux/AppArmor and other cruft.
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. /:softland:~$ uname -a /:softland:~$ ld -v /:softland:~$ gcc -v ../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++
Welcome to Linux SLS 1.05. Type "mesh" for a menu driven interface.
Fresh installations should use "syssetup" to link the X servers, etc.
Linux softland 4.16.14 #1 SMP PREEMPT Sun Jun 10 02:52:51 EST 2018 x86_64 unknown
GNU ld (GNU Binutils) 2.30
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:
Thread model: posix
gcc version 7.3.0 (GCC)
In the future you should keep your poverty to yourself.
MegaStrawman!
Systemd design is deliberately based on dbus specification as THE defacto IPC implementation. It's basing a lot of its functionality on IPC and well duh, it hard depends on it. But oh hey, it doesn't specifically depend on dbus. Ever heard of dbus broker that's under development? Do you know what it's all about? I'd say you don't.
You can write your own Noobus 3000 (tm)(r)(c), and as long as it supports the same interfaces, it can be used instead. So uhm... Nope. You're wrong.
Comment removed based on user account deletion
Comment removed based on user account deletion
You've quite obviously never used the SysV answer to IPC. Don't be a dunce, look this shit up before posting since you don't work with IPC technologies. (d-bus is the modern IPC mechanism)
You don't get to have d-bus be some kind of criminal, it is in fact a required part of a modern *nix system, because IPC is a thing. And no, nobody is even willing to attempt use of semaphores anymore.