Slackware is 21 Years Old
slackblogs.blogspot.com
slackblogs.blogspot.com
Turns out Slackware still rocks! It's simple and literally just works. Slackbuilds.org wasn't around when I first tried Slackware and my life is a lot easier than it was back then. It's great. Happy birthday guys!
Strangely, with the way containers are going, I think I'm actually becoming more likely to head back towards Slackware's userspace as a well tested and documented minimalist environment, in the near future than in the recent past.
I tried again today - it's completely different from what I remember and very straightforward. I am installing it now (under VirtualBox) - wish me luck!
It can skip the "modern" desktop crap though, that's cool. They don't distribute Gnome anymore, so it doesn't cram hundreds of libwhythefuckisthisalib and libgnomewhythefuckisthisagnomelib and their dependencies on the drive, and all the KDE stuff is nicely tucked away so you don't have to install it.
I remember when Slackware fit on a single 3.5" floppy. There was a second disk, but you only needed that if you wanted to install X, and why would you want X when you had virtual terminals you could just switch between?
I loved that Slackware didn't try to move stuff around in third party software to fit idea about a official disc layout.
Also the init system made so much more sense (still do I think).
Slackware is a wonderful distribution for people who want to learn Linux, not just use it.
I'd tried every major distro before settling on Slackware sometime around '99 and that's when I finally learned Linux.
I'm using Arch today and to me it's a very similar philosophy with some bonuses. If it weren't around, I would surely be using Slack.
I was tired of not knowing what was inside my distro, nor how it worked... so one day I decided to build my own distro (following the very good Linux From Scratch book, and then later the Cross-Linux From Scratch book).
It's even more bare-bones than a base arch or slackware -- but the best part was knowing exactly how everything worked, and no longer fearing of changing something, because I understood what it was doing now.
The experience and knowledge of "rolling my own distro" is very applicable elsewhere -- from understanding kernel panics better, to understanding "dependency hell", to how the entire boot process even works.
A linux distro is really a thing of beauty once you understand what is going on under the hood.
LFS was definitely a helpful step to "dive deeper" though.
The system is so neatly designed that you don't even notice the lack of automatic dependency resolution. This is simply because of the sheer breadth of choices you have when it comes to installing software on Slackware.
In short, it's the last bastion of sanity in Linux.
People told me to reinstall. I didn't, I tracked down all the tgz's and hacked on installpkg to regenerate /var/log/packages without reinstalling. Of couse all streaming over a mounted curlftpfs. Oh what a rush.
% ls ~/tmp/desaster/
installpkg
local-pkgs
root
slackware64
This was possible because I knew which series I installed at date X. I knew my last security updates were at date Y and which custom (self-built) packages I had installed. Slackware is so simple, so sane, so beautiful. A hallmark of software engineering.I never really felt this to be a problem. Slackware has everything you need in the installer you hardly ever have to install new stuff for most of the standard things.
Most of the time I use slackpkg to apply updates and version upgrades, sbopkg for third-party software by handpicking the dependencies, and precompiled packages for software with lots of dependencies that are tedious to sort.
It's clean, easy and avoids the bloat of unneeded packages lying on your system.
(I used Slackware from 1994 to ~2005.)
I've tried other distros like Open Suse and Ubuntu but they weren't for me. I don't need all the overhead to do simple thing that can be done by editing a text file. (Mint is pretty nice though... I install it sometimes for friends and family members).
I appreciate the effort behind apt-get type package mangers, but often they often aren't up to date. With a slack build I get the latest source and know exactly what I am getting rather than installing some mysterious black box binary. Sure, apt-get might save 5 minutes but I'd rather spend the 5 minutes and do it right. Just my personal fetish.
If you are new to Slack or Linux in general I recommend trying Slax or Porteus. Since they are live, you can change whatever you want and experiment, and just restart your machine when you inevitably bork something. This is how I came to Slackware in the first place. I needed a live distro for a kiosk I was building (was an Open Suse user at the time) and started taking apart and re-assembling Slax. Eventually the light went off in my head and I saw the beauty of simplicity and have never looked back.
Man those were the days, having to manually mount your usb stick with the 2.4 kernel. Dropline Gnome (still alive I see http://www.droplinegnome.org/) made Slackware a lot easier to keep up to date and pretty and slapt-get provided a nice update mechanism. I went to Gentoo afterwards and then to Arch, I haven't looked back for years now. To bad DO dropped Arch support so now I'm using Debian on the server VM's.
Remember Patrick got sick and the whole community was sending drugs? Nice.
And that whole drama about jumping version numbers...
It was very exciting times. I learned to build my own kernels which took hours on the crappy old dell I owned at the time, but very satisfying. It was even more exciting when I managed to get a Novell NE2000 clone to work with it as well and set up my first web and FTP server in my bedroom and then got it to talk to my Hayes compatible modem and Demon Internet.
Happy hacky days :)
I use CentOS these days, mainly because it's our company standard, I must go back and give it another spin. Congrats Slackware!
Here is the contents:
For information about getting "Bob" in your life, send $1 to:
Church of the SubGenius
P.O. Box 140306 Dallas TX 75214 USA ($2 US extra if outside US)
http://www.subgenius.com
I'm pretty sure the URL has changed. It was on sunsite.unc.edu.I'd like a minimal install base right now (and manually picking this in the installer ain't that easy), but back in '95, having every kind of editor, programming language, window manager, TeX etc. on disk was awesome. And then I started looking at comp.os.linux.announce and sunsite to see what's new and current and installed that manually (and dependency tracking wasn't an issue at all because a) most libraries on disk anyway -- certainly no silly "-devel" packages and b) we didn't have that many dependencies back then, when "based purely on Xlib" was a badge of honor...
I think the best way to do this currently is to select the categories of packages and then choose a "Full Install" (the warning that it will install almost 8GB of software is a little confusing as it only installs what was selected on the previous screen).
I think you can do quite a bit with just the A, AP and D sets.
I cannot remember anylonger the exact version.
It was the last version of Slackware to use a.out executable format and IDE ATAPI had just recently been added. My CDROM IDE wasn't supported during boot time, only after installation, hence the workaround.
Dogfooding the Web site. I learned quite a lot from zipslack, a live distro booted from an Iomega Zip disk.
Edit:http://www.linuxquestions.org/questions/interviews-28/interv...
Some historical stuff
And Ubuntu?
I tried it in 2008. Decided it used way too much RAM. Scraped it off.
Linux: You've come a long way, baby!
Instead, I used MCC Interim Linux to get a base set of bits since it had such a tiny foot print. I also somehow managed to cobble together X11 and get it working, but I seem to remember it being a real pain in the ass.
Coincidentally, my first X11 background image was also of JR Bob Dobbs, but I wasn't running Slackware.
What amazed me that time was Slackware was developed and maintained by a single person "Patrick Volkerding" Long live linux community!
In its heyday (mid-late 90s), Slackware _was_ Linux for noobs. I still remember downloading all those disk images via modem.