I ran it on my desktop and an old (old in the early 2000s!) laptop with 32 MB of RAM, and learned a TON. It's the perfect generic "Linux" system, and you can take it in any direction you want, but you have to do it yourself.
Funny enough, I also got too busy and moved to Debian.
It's romanticized a lot, but boy was it painful! hear my story and weep.
In 1995 I got slackware with a textbook from the university library. I had a brand-new 486 paid for by a dad with 2 other kids in college and nothing more than a factory job to pay for things.
So my 486 had no CDROM. And it only had 4MB of RAM. And a pirated version of DOS, until I got slackware.
After 3 months of saving from weekend work I made enough to get a shitty soundblaster pro clone. And then I returned it for another unit, because, as I complained to the store owner "this doesn't work". When the replacement didn't work either I realised it must be my computer, more specifically, those "drivers" provided on the floppy disk were for msdos :-/
So then I started reading a bit, and digging into the driver sources, and reading the little pamphlet that came with the soundcard. "Hah!" I thought, "the IRQ channel for the soundcard appears to be hardwired!"
And thus begun the longest 3-day weekend of my short life up to that point; Linux had no modules, everything was compiled into a single binary image. You have any idea how long it takes a lowly 486 with 4MB of RAM to compile a kernel?
The entire weekend was "make this change, type make $SOMETHING, then wait for 50m, then watch it fail to boot, then examine how far the bootloader got, then boot with previous image, then undo that change and repeat the process".
Eventually had the soundcard working though. On a system on which no bloody games would run ...
My neighbor told me to try Linux, and my computer at the time was a Mac (old PPC 603e cpu), which I’d put a PC Voodoo3 in and flashed it with a Max bios. Couldn’t afford a Mac card, PC ones second hand were much cheaper.
Anyway, the basic X frame buffer was so slow I needed accelerated 2D. The Voodoo3 driver was available as a patch to 2.2.18 and I was on 2.2.16. So, had to learn to patch and compile a kernel as one of my first acts of learning Linux.
But it got me accelerated 2D which made X bearable, so I could use KDE (2) or Gnome (1.4, still my fav).
After that it was enough to get me to build my next desktop as a Linux PC through college.
This is me still when I try to build Gentoo
It just keeps working, and when a new release comes out, it keeps working better. Better than I can say for my experience on most other distros. That it moved to pulseaudio eventually in the first place was a bit of a gasp moment, but it's generally been very good at adhering to the Unix design philosophy -- a rare thing these days.
What hooked me on NetBSD was that early on I had a experience with a laptop where audio was not working. After a small amount of reading, I edited a file, recompiled the kernel and voila I had audio. The fact I was able to do that as a total novice was what made me a loyal user for the ensuing decades.
After many many years of using Slackware, I still believe NetBSD was used as inspiration for the design of Slackware.
BTW, I really like pkgsrc, I wish that ended up being a standard for Linux instead of all the multiple package/dependency managers that exist.
And NetBSD is really my favorite BSD, I only wish it worked without a minor hardware issue on the Laptop I have. I may end up putting in a PR for 10.0 BETA once I am sure of the issue.
Back in '92 I was interested in 386BSD, but told to check out linux (which was at 0.12 at the time), back then it was the root/boot disk distro, then mcc, then slackware.
The Nvidia chip gets very hot, even when I disable it on boot. The CPU Temp stays low.
The Nvidia chip is in the lower left corner of the Laptop, and it cannot be disabled by a BIOS Switch. Since NetBSD has Nouveau support, I want to be sure 10.0 BETA supports that specific chip before deciding what to do.
FWIW, same thing heat issue happens with OpenBSD, but OpenBSD has no Nvidia support, luckily OpenBSD is able to ignore it. Slackware, no issue with Nouveau and heat.
If booting into something barebones leaves everything cool, and depending on how long it takes for the chip to get warm, perhaps you could move a `for (;;);` further and further down into the OpenBSD kernel and find the point things get cranky that way.
Extremely hacky approach though, I'll definitely concede that point >.>
(But if you want to try it, I would wholeheartedly recommend looking into something like iPXE, which would let you download each test kernel over HTTP at boot time and make the iteration process tolerable. This assumes you have a second machine though...)
Slackware lets you do things your way.
Congrats Patrick and Slackware.
I stopped using it when I had less time for tweaking my computer in my life (I moved to Debian), but it was a very formative experience. Good defaults, but with all the power to change whatever you want and the simplicity to make it manageable.
Happy birthday Slackware!