Honestly, it sucked. Like most computing at the time. Everything came on a ton of floppy disks, it was impossible to update online unless you had a good connection (which nobody did), and you had to do everything by hand, including compiling a lot of stuff which took forever. I mean, I’m glad I got the experience, but I would never wanna go back to that. It sucked.

Alrighty, old Linux user from the earliest of days.

It was fun, really great to have one-on-one with Linus when Lilo gave issues with the graphic card and the screen kept blank during booting.

It was new, few fellow students where interested, but the few that did, all have serious jobs in IT right know.

Probably the mindset and the drive to test out new stuff, combined with the power Linux gave.

It wasn’t too early, maybe 1997.

I was like 12 or so and I had just installed Linux.

I figured out, from the book I was working with, how to get my windows partition to automaticallyount at boot. Awesome!

I had not been able to figure out how to start “x” though.

So I rebooted into Windows, for on EFnet #linux, and asked around.

Got a command, wrote it down on a slip of paper, and rebooted into Linux.

I should mention, I also hadn’t figured out about privileges, or at least why you wouldn’t want to run around as root.

Anyway, I started typing in the command that I wrote down: rm -rf /.

I don’t have to tell you all, that is not the correct command. The correct command was startx.

After I figured it was taking way too long, I decided to look up what the command does, and then immediately shut down the system.

It was far too late.

Clumsy. Manual. No multimedia support really. Compiling everything on 486 machines took hours.

Can’t say I look back fondly on it.

BeOS community was fucking awesome though. That felt like the cutting edge at the time.

“Please insert Slackware disk Set A disk 3”

I started using Linux right in the late 90’s. The small things I recall that might be amusing.

1. The installation process was easier than installing Arch (before Arch got an installer)
2. I don’t recall doing any regular updates after things were working except for when a new major release came out.
3. You needed to buy a modem to get online since none of the “winmodems” ever worked.
4. Dependency hell was real. When you were trying to install an RPM from Fresh Meat and then it would fail with all the missing libraries.
5. GNOME and KDE felt sincerely bloated. They seemed to always run painfully slow on modern computers. Moving a lot of people to Window Managers.
6. it was hard to have a good web browser. Before Firefox came out you struggled along with Netscape. I recall having to use a statically compiled ancient (even for the time) version of Netscape as that was the only thing available at the time for OpenBSD.
7. Configuring XFree86 (pre-cursor to X.org) was excruciating. I think I still have an old book that cautioned if you configured your refresh rates and monitor settings incorrectly your monitor could catch on fire.
8. As a follow on to the last statement. I once went about 6 months without any sort of GUI because I couldn’t get X working correctly.
9. Before PulseAudio you’d have to go into every application that used sound and pick from a giant drop down list of your current sound card drivers (ALSA and OSS) combined with whatever mixer you were using. You’d hope the combo you were using was supported.
10. Everyone cheered when you no longer had to fight to get flash working to get a decent web browsing experience.

The danger of poorly configuring your XF86Config in a way that could irreparably damage your giant CRT monitor was thrilling.

It was S.u.S.E. Linux 5.3

Great manual.

I was lucky that my NIC, graphics and sound card were supported out of the box.

But everything was still much worse than on Windows.

But I could taste the freedom.

Now all my devices run on Linux (except my Nintendo Switch).

You got it from a friend on a pile of slackware and floppies labeled various letters. It felt amazing and fresh, everything you could need was just a floppy away.

Then we got Gentoo and suddenly it was fun to wait 4 days to compile your kernel.

All my homies who were into it were like “everything is free you just have to compile it yourself”

And I was like “sounds good but I cannot”

Then all the cool distros got mature and feature laden.

If you were a competent computer scientist it was rad.

If you were a dummy like me who just wanted to play star craft and doom you wasted a lot of time and ended up reinstalling windows.

Before modularized kernels became the standard I was constantly rerunning “make menuconfig” and recompiling to try different options, or more likely adding something critical back in :-D

Spent a week getting the audio driver to work so I could finally figure out how to properly pronounce “Linux…” and I still couldn’t.

Spent like $50 on floppy disks and like 2 days labeling them by hand before printing out the 20 pages of instructions, formatting my hard drive and installing Slackware. Realized I didn’t actually know any unix commands. Paged a friend.

winmodems and modelines were problematic but it was liberating to be able to tinker.

and walnut creek was doing the Lord’s work.

Prior to the website rpmfind.net, installing software was to put it mildly, a chore. Due to package dependency, you’d start the compile, and it would fail due to missing libraries. You’d then go out and find those libraries, only to have them fail on compile…due to missing libraries…it would go on like until you finally were able to compile the original package - at this point though you compiled it out of sheer spite for the universe that put you in that position.

I rate the experience a solid 5/7

The absolute best thing about it was that after suffering under Microsoft’s shitty operating systems for years, you were running a Unix-like on your own hardware. That part was amazing.