Do you remember the dreaded 'floppy disk is probably unreadable' sound during installation of any software on floppy?
I soon figured out that it was easy to skip the cdrom altogether and make a minimal install using just the boot disk and ftp. So easy yet you had to be deliberate and understand what you were doing. Such a great learning exercise.
I never thought of a T1 as "slow" until I started downloading CD images for Linux distros. The first cable modem connections I had were so much faster for downloads.
Funny learning how slow those are by today standards.
T1, T2, T3, OC-3, OC-12, and OC-48 are terminologies you don't hear anymore.
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!
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.
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 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.
Slackware lets you do things your way.
Congrats Patrick and Slackware.
I learned so much from Slackware and basically owe my livelihood to it. Everything from compiling the kernel to trying (and failing) to get X11 working. On the flip side, I'm super glad I don't have to do that anymore and can just use Linux without having to fiddle with the internal parts.
So many hours recompiling kernels. My 4MB-equipped 486 took about 8 hours per. I only realized many years later after somehow finding the $400 for a memory upgrade, that it was only slow due to swapping. Going from 8 hours to 10 minutes was eye-opening.
X11 failed to run, for the same 4MB reason. I mean, it would launch, but I want to say it took 20 or 30 minutes.
Anyway, happy birthday, Slackware!
I am posting this from Slackware 15.0 right now, my main driver, but I do boot a BSD once in a while. If not for Slackware, I would have left Linux for a BSD years ago.
I hope Slackware can avoid all what I believe are crazy changes occurring in Linux Land. Already Slackware was forced to import PAM, but in good Slackware fashion PAM stays out of my way, so not a big deal.
I have used then all to test what I developed on Slackware for use in work, I like to be sure what I due can work on most "free" OSs. But their PAM, from what I understand is a different code base (bsdpam). But in these cases, PAM is invisible to me too.
I ran into a ton of issues installing sound cards, running X11 on a cyrix mediaGX card. And learned how to compile kernels, ask questions on mailing lists and debug C programs.
Truly the start of my serious engineering career haha.
Loved seeing how others have similar experiences and are all on hn. Small world.
Back in 2015, I worked with Pentium III -class Cyrix processors on a legacy but still supported and in-production embedded system released in the mid 2000s AFAIK. But I never came across a Cyrix-based consumer PC or laptop (growing up in Southern California). Were Cyrix processors common on consumer PCs in India?
[0] http://www.slackware.com/changelog/stable.php?cpu=i386
I had to copy all the floppy images from the CD-ROM into the hard disk and then boot the installation from floppy, as my IDE CD-ROM still wasn't supported by the Linux kernel 1.0.9, and my Trident card was downgraded to 800x600, as X couldn't do 1024x768 with it.
Happy birthday Slackware.
EDIT: kernel version.
I remember trying to figure out how to compile the kernel for everything in my desktop.
X11 MODELINES, ipfwadm, BNC network cards, and PPP, tcl/tk shell scripting..
BasicLinux had a great community and introduced me to mailing lists. I learned a lot about how Linux works, tracking down dependencies with ldd and modifying config and init scripts. After a year or so of playing with BasicLinux, I moved on to Slackware, but continued to use the mailing list for help.
So happy 30th to Slackware and cheers to anyone who provided assistance on the BasicLinux mailing list!
Funny that you mention USENET. I'm subscribed to about 20 newsgroups, using Claws-mail. It is quite nice that they're separate from my other mail accounts.
I might be mistaken, I think I had a CD rom instead of floppies.
These days I run Arch Linux, which is the closest I can get to total control of every aspect of my system (without sacrificing prebuilt binary packages - I do not have the patience to wait for my browser to be built from scratch!). I'm quite happy with my understanding of the modern Linux stack! Though I still look longingly at the early days of Linux, when you really had to do everything yourself, and bringing up a Linux system from scratch was worth serious bragging rights.
Do you think I would gain something by trying out Slackware today in 2023? Perhaps see how Linux used to work in the good old days, without SystemD or a fully working Xorg? And should I do so with modern Slackware, or an older version to truly experience the floppy install process (hardware support may be an issue--might try to source an ancient Thinkpad)?
While coding BASIC and Z80 Assembly were a bit of challenge, but doable, installing a UNIX based OS is another level.
Regarding trying Slackware today, I think it would be more interesting to try out another UNIX like one of the BSDs, or getting hold of HP-UX, Solaris, Aix somehow, as they do provide a complete different experience, while Slackware it is still a Linux distribution, dispite the differences.
your keyboard?
Was saying that I managed to disable admin access for my user, so I had the pleasure of obtaining a recovery root shell and learning about the sudoers file.
Without Slackware, I would not have learned how to build a web server, wouldn't have learned about UUCP (which thankfully I haven't needed to use in about 20 years)... basically the entire course of my life would have changed.
(Entirely random aside: I returned the opened BSD disks for a full refund. Remember when you could do that without them assuming you copied the disks?)
Also with regards to UUCP, it appears there are some modern uses for it [0]. I have no perspective with regards to UUCP but from someone who used it (if it doesn't bring back painful memories), do you recall what you used it for or what using it was like? Essentially email + USENET newsgroups + FTP wrapped into one protocol?
[0] https://en.wikipedia.org/wiki/UUCP#Current_uses_and_legacy
It only took about 30 years for Microsoft to accept POSIX matters, regardless of its caveats.
Naturally there were a couple of factors that led to that change of mind.
Back on the subject, I have spent endless hours going through the packages on Slackware, specially GCC, given my interest into compilers.
Edit: It was probably a 386, memories of that time are sketchy.
Honestly, now that I think about it, it might have been a 386 but I was entirely sure it wasn't. Memories are weird.
[0] https://news.ycombinator.com/item?id=28565745
[1] https://tldp.org/HOWTO/META-FAQ-2.html
[2] https://mirrors.slackware.com/mirrorlist/
[3] ftp://ftp.osuosl.org/pub/slackware
[4] ftp://mirrors.xmission.com/slackware/
Back in the olden days it ran just fine on a Compaq Deskpro 386SX but needed a whopping 4MB of RAM.
[0] https://www.theregister.com/2023/05/03/linux_distro_hopping/
[1] https://news.ycombinator.com/item?id=26503724
[2] https://news.ycombinator.com/item?id=36682277
[3] https://www.computinghistory.org.uk/det/61777/Linux-FT/
[4] https://www.linuxjournal.com/article/139
[5] https://www.linux.co.cr/distributions/review/1995/0416.html
[6] https://techmonitor.ai/technology/lasermoon_touts_inexpensiv...
[7] https://en.wikipedia.org/wiki/Yggdrasil_Linux/GNU/X
[8] https://en.wikipedia.org/wiki/Softlanding_Linux_System
[9] https://en.wikipedia.org/wiki/Windows_3.0#System_requirement...
I can't remember what it was like running Ubuntu 12 and that was only ten years ago, Lasermoon was 30...
Everything was command-line, not least because I didn't have enough space to install X. It worked okay. I feel like the compiler might not have been gcc? Not sure. I know that around the late 90s there was gcc and egcs, which was kind of a fork, that re-merged - I used that on Redhat 6, not RHEL6 but Redhat 6, with Gnome, and the K Desktop Environment as an option (the first versions of both!).
I guess I could trail about and see if I could find images of Lasermoon and try to install it, probably on a VM. If you're interested I could make a video, I guess?
Edit: this was the CD! https://archive.org/details/Shop0396
[0] http://ftp.osuosl.org/pub/slackware/slackware-14.0/ChangeLog...
[1] http://ftp.osuosl.org/pub/slackware/slackware-14.1/ChangeLog...
[2] http://ftp.osuosl.org/pub/slackware/slackware-14.2/ChangeLog...
[3] http://www.slackware.com/security/viewer.php?l=slackware-sec...
[4] http://mirrors.slackware.com/slackware/slackware-current/sou...
I switched to Gentoo after Slackware because everything was working just fine and I got bored. After that I learned that my free time is better spent on gaming and I switched to Windows 7. I came back to Linux after few years and damn - systemd took me by surprise. I never learned to use it properly because it's so much more complicated than my beloved Slackware SysV Init.
Congratulations to Patrick Volkerding - managing distro for 30 years is no small feat. Happy hacking.
That's why i switched from Redhat 5.2 to Slackware and never looked back.
In redhat you had circular dependencies: libfoo requires package libbar and libbar requires package libfoo.
Solution: use rpm --force
Also an RPM package will refuse to install when a dependency was not found (when you compiled and install the library yourself).
Needless to say, for my first time using linux, it didn't work out. But a short time later I was dual booting mandrake & slackware 8.1. Ahhh...the sweet nostalgia of gnome 1.4.
Youngin's these days don't have any challenge left. Now where's my cloud to yell at? And why are you on my lawn?!
While not my first distro, that would be the copy of Red Hat Linux 5.2 I got with the Unleashed book, it is the distro I'm most comfortable with.
I ended up deleting windows from my pc by destroying all partitions...It has been quite a ride :-)
[0] https://linuxnewmedia.square.site/ [1] https://www.linux-magazine.com/
[0] http://www.slackware.com/lists/archive/viewer.php?l=slackwar...
[1] https://en.wikipedia.org/wiki/Slackware
[2] http://www.slackware.com/lists/archive/viewer.php?l=slackwar...
[3] https://mirrors.slackware.com/slackware/slackware-8.1/Change...
Still have the warm fuzzies every time I think of it.
Some links just in case you want to re-live the experience :-P
http://ftp.slackware.com/pub/slackware/slackware-3.3/bootdsk...
I feel like Arch Linux has taken up that mantle in today's world to a certain extent. I'm glad there are distros like these.
Happy birthday Slackware!
My Linux journey started in May 2000 with Red Hat 6.2 (a Deluxe boxed edition). I then upgraded Red Hat up to 7.2, and then went to Mandrake, from 8.2 and up to 9.2. Then, a special version of dependency hell that was the Mandrake 9.2 framebuffer console forced me to switch to Slackware, which I was already using for experimenting.
This Register article hits it in the nail; Slackware might look primitive but it's in fact quite advanced. It's my regular desktop driver, working as a lawyer, translator and university lecturer. There are many things who are automatically detected and configured, and whatever stuff you had to configure by hand, it lives on legendarily over and over.
I had to configure stuff by hand, yes; but I have configs from those early days almost 20 years ago which still are there, unmodified. They just keep working.
So, if you would like a reasonably stable, fast, modern and simple Linux system, and you are not afraid of using a text editor, then you should give Slackware a try.
I believe I destroyed a lot of important data that day (what is "a backup"?), but other than that, good times. :-|
I used it as a very solid file server for a long time.
"Very good year. Nearly as old as I am!"
Hail Patrick!
Interesting, I wonder who did the port?
All Mac for a while now