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.

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.

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.

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.

LI

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.

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

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.

stacks of diskettes, for every operating system.

would routinely spend hours doing an install only to hit a block and have to reinstall DOS to have modem access to get help on usenet. Then hours of reinstalling to move forward and repeat on another issue.

I really loved it though, it was a massive upgrade over DOS and windows on a 286.

No audio, no WiFi, no well-established communities, sparse software selection, but total freedom on an alternate OS. I tried it out in the late 90s with Red Hat, left, came back about 5 years later in the early 2000s and stayed forever. SuSE 9.2 was amazing.

Well, I was an Amiga user. That was already unix-like, preemptive multitasking, etc. It was fading fast in the early nineties, and while i was already working in I.T., I was not interrsted in using Windows 3.11 and 95, so I began playing with Slackware Linux. I figured it was a good way to get comfortable with “real” I.T…

I learned Bash and had to compile most of the software i wanted to try. Since, like all programmers, I’m lazy, I wrote some simple scripts to build the code and make them into packages (tgz) for Slackware. This took tedium out of the work, and i could use the packkage manager to install and remove them.

Those were rough days for desktop users, though. I really had to use windows when i needed to pass output to “normies”. I tried several window manager and desktops, and eventually landed on Ubuntu.

My first time trying out Linux was with a bootable CD from a PC gaming magazine. It was Corel Linux. If I recall correctly it booted into KDE.

Unfortunately on my system the mouse cursor was invisible. The mouse worked, I just couldn’t see where the cursor was. My brother who was using Linux full time couldn’t help me fix it.

There was a similar question a while ago with some nice reads in the answers :)

lemmy.ml/post/17575792

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.

Someone-being-bratty-on-IRC: […]
Me: We’re going to take away your internet access if you don’t behave. 
Bratty: Fuck you! You can’t do tha
5 minutes later…
Bratty: How did you do that??? 

.

I started using it before distros were really a thing. I got as far as having something that would boot to a shell, but then since I was 14 I had no idea what I was supposed to do.

Backed off until I bought a Slackware book that came with a CD. Then I had the fun of trying to get X working. Manually entering frequencies for your monitor was scary, because if you got it wrong you could damage the monitor.

Then I had a fun problem of either my modem would work, or my sound card would work, but never both at the same time.

Honestly I never got a system which I could actually use for anything, but I was a kid having fun, and it taught me to not be afraid of the computer.

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

Why not just install an old version in a VM and find out?

But remember, no search engines for troubleshooting, forums and printed matter only. (And mailing lists and IRC, but they’d probably tell you to Google it, which is off limits for this exercise.)

First time I format the whole disk, all msdos data (games) lost. I managed to install it then I opened vim to edit a file and I couldn’t get out of vim I know it’s a cliche, but there is real. To get out I have to call a friend, using the landline, the one who lends me the floppy disks (or maybe it was magazine cd) and ask he how to get out, he says, just press Shift and Z twice.

Looking through music and budget software CDs at a computer store or a college vendor table, there would be one with a penguin or BSD mascot. It wasn’t like the other discs that had DOS shareware games or utilities. The CD rom drives were 1x speed, attached to a card on the ISA bus, without plug and play, so it needed an interrupt number that didn’t collide with other cards. The install process was curses based, with no mouse. There would be much time spent figuring out how to partition the drive, usually after buying a book. Back then, computer book sections were huge. The software install dialog had one line description per package, and it wasn’t easy to tell what they did. Then there was setting up X Server and choosing a window manager. Not all video modes were supported, so it took a lot of trial and error with editing config files and resolutions before the the window environment would work. This was before home internet so it would take a weekend or all week to figure out. The only accessible communities in many parts were dialup bulletin boards, unless there was access to a college computer lab with a mosaic or netscape browser. At this point it was realized that I lived in a tech desert, quit my retail job, and moved.

My first experience was with two floppy images I found on “So much shareware! Vol.2”.

It was labeled Linux 0.99b, no distro. It was not of much use to me at the time.

A couple of years later I got my hands on Slackware 2.0 on CD. So much time spent compiling your own kernel, because no modules and the whole thing had to fit in main memory (640kB). So much time spent fiddling with xf86config hoping you wouldn’t fry your CRT.

Good times.

Then came gentoo, which had package management. No more did you have to browse sourceforge for endless dependencies to install something. No more did you have to re-install slackware on your root partition to update. So user-friendly in comparison.

We spent a lot of time on IRC.

MUDs kind of bridged the gap between IRC and games.

I remember spending a lot of time playing abuse, snes9x, quake + team fortress and quake2 + action quake.

<img alt="" src="https://lemmings.world/pictrs/image/02c0d25f-81ad-48c6-b6c2-dd20bd2b55b3.jpeg">

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

I remember building the kernel with the NE2000 drivers and having a network card for just installation and getting the 3com or RTL driver source over to the new install, then compiling those drivers, installing them, and downing the system to put the proper card in. There was a very small subset of sound cards and video cards that worked reliably. The notion that Linux was the OS where hardware just worked out of the box was ludicrous.

The DEs were pretty horrible and the software to use on them was scant. So desktop Linux was a pipe dream. I used Linux entirely as a security/server appliance. I built a couple hundred iptable/ipchains firewalls for businesses out of recycled pentium type desktops until hardware firewalls became a thing, it was fairly lucrative for a while there.

<img alt="" src="https://lemmy.dbzer0.com/pictrs/image/18537484-74c5-43de-8f60-0e83d06418ac.webp">

“Please insert Slackware disk Set A disk 3”

I got a very early version of Debian from a friend when I was in college. I had a very old computer gifted to me but couldn’t get Windows to install. I ran that badboy with no window manager, just text. I used elinks for my web browser and pine for email. VI was where I wrote my papers. Drivers were a problem, so I had to save papers on a disk to print from a computer at a library.

Imagine a pile of floppy disks, with stuffs inscribed on it that you never heard of…

… will you insert one into your computer and reboot it?

I was born in the 80s and never even though about Linux until very recently.

<img alt="Pain" src="https://lemmy.ca/pictrs/image/8b0a702a-7880-49cd-9f18-4c3e752338f1.jpeg">

Just raw dogged linux and loved it. Lot more stable than windows 95/98

In the 90s, it was hard :-)

It made sense to recompile the kernel to make it fit your hardware.

It was a mess to find peripherals that were working with Linux.

Back in my day we had to get our Internet at the village Internet well. I remember the dialup modem noises it made as you pulled the bucket up.

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

and walnut creek was doing the Lord’s work.

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.

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.

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).

Well, in the 90’s I managed to essentially brick two NIC’s by tinkering with the tulip driver on command line. In the distro I used it had to be done manually and I still have no idea as to what happened inside those NIC’s, but they sure didn’t work ever again. Yes, I made the same mistake twice.

I was just looking through old books and noticing my Yggdrasil manual the other day. That was one of the earliest plug and go cd-rom distributions. Before that was e.g. Slackware and the early Debian, both of which involved big piles of floppies. I also remember sending Linus an email and getting an answer. I’m sure he is too much of a busy celebrity for that now.

Hard

94-95 school year for me. Prior to win 95. Honestly OS2 warp was the tits then, blew windows and linux away. But the cool thing about linux was that you could pull a session from the college mainframe and then run all the software off campus. Over a modem. Pro E, maple, matlab, gopher, Netscape, ftp/fsp, irc, on and on. Once you had X going on your 486, you were good to go.

But honestly, it was nerd sh$t. Dos was king until win95. And then nobody looked back until win8 made us realize Microsoft had started sucking.

We didn’t have -R, you had to go into every subdirectory and run the command manually.

LUGs were very important back then especially when you were new.

I spent what felt like many moons trying to compile Gentoo when I was a kid. There was only the wiki and a gritty forum for getting answers, nothing in real-time. I didn’t have very much knowledge of the kernel or messing with modules, and was certainly lost on getting a desktop environment going even after I got past the kernel part.

It was such an experience, I decided to become a janitor.

ETA: also this guy (not strictly linux, but same vibes)

<img alt="BSD Daemon" src="https://upload.wikimedia.org/wikipedia/commons/thumb/4/40/Daemon-phk.svg/500px-Daemon-phk.svg.png">

it was garbage.

servers already worked well for the time, but desktop was rough.

Reading how-tos(may be the source code too) are all you needed. No need to listen random stuff from some random YouTubers. Ppl can read that time. Books and magazines did exist.

If you wanted to run Unix, your main choices were workstations (Sun, Silicon Graphics, Apollo, IBM RS/6000), or servers (DEC, IBM) They all ran different flavors of BSD or System-V unix and weren’t compatible with each other. Third-party software packages had to be ported and compiled for each one.

On x86 machines, you mainly had commercial SCO, Xenix, and Novell’s UnixWare. Their main advantage was that they ran on slightly cheaper hardware (< $10K, instead of $30-50K), but they only worked on very specifically configured hardware.

Then along came Minix, which showed a clean non-AT&T version of Unix was doable. It was 16-bit, though, and mainly ended up as a learning tool. But it really goosed the idea of an open-source OS not beholden to System V. AT&T had sued BSD which scared off a lot of startup adoption and limited Unix to those with deep pockets. Once AT&T lost the case, things opened up.

Shortly after that Linux came out. It ran on 32-bit 386es, was a clean-room build, and fully open source, so AT&T couldn’t lay claim to it. FSF was also working on their own open-source version of unix called GNU Hurd, but Linux caught fire and that was that.

The thing about running on PCs was that there were so many variations on hardware (disk controllers, display cards, sound cards, networking boards, even serial interfaces).

Windows was trying to corral all this crazy variety into a uniform driver interface, but you still needed a custom driver, delivered on a floppy, that you had to install after mounting the board. And if the driver didn’t match your DOS or Windows OS version, tough luck.

Along came Linux, eventually having a way to support pluggable device drivers. I remember having to rebuild the OS from scratch with every little change. Eventually, a lot of settings moved into config files instead of #defines (which would require a rebuild). And once there was dynamic library loading, you didn’t even have to reboot to update drivers.

The number of people who would write and post up device drivers just exploded, so you could put together a decent machine with cheaper, commodity components. Some enlightened hardware vendors started releasing with both Windows and Linux drivers (I had friends who made a good living writing those Linux drivers).

Later, with Apache web server and databases like MySql and Postgres, Linux started getting adopted in data centers. But on the desktop, it was mostly for people comfortable in terminal. X was ported, but it wasn’t until RedHat came around that I remember doing much with UIs. And those looked pretty janky compared to what you saw on NeXTStep or SGI.

Eventually, people got Linux working on brand name hardware like Dell and HPs, so you didn’t have to learn how to assemble PCs from scratch. But Microsoft tied these vendors so if you bought their hardware, you also had to pay for a copy of Windows, even if you didn’t want to run it. It took a government case against Microsoft before hardware makers were allowed to offer systems with Linux preloaded and without the Windows tax. That’s when things really took off.

It’s been amazing watching things grow, and software like LibreOffice, Wayland, and SNAP help move things into the mainstream. If it wasn’t for Linux virtualization, we wouldn’t have cloud computing. And now, with Steam Deck, you have a new generation of people learning about Linux.

PS, this is all from memory. If I got any of it wrong, hopefully somebody will correct it.

Contrary to other OSes, the information about it was mainly on the internet, no books or magazines. With only one computer at most homes, and no other internet-connected devices, that posed a problem when something didn’t work.

It took me weeks to write a working X11 config on my computer, finding all the hsync/vsync values that worked by rebooting back and forth. And the result was very underwhelming, just a terminal in an immovable window. I think I figured out how to install a window manager but lost all patience before getting to a working DE. Days and days of fiddling and learning.

Stuff needed tweaking more wine worked almost never even for basically window’s programs. Configuring Xfree86 was black magic. Running Startx at the terminal prompt was like rolling the dice. Distro choice was smaller and it was really a choice. Since the child distros were less of a thing. You had Debian , Redhat, Slackware, and SUSE. All were very different at a fundamental level with packaging and philosophy. Also it was way more common to buy boxed copies of Linux distros with big thick manuals that helped you get it installed and take your first steps with Linux. It reminded me of when I first got my TI 83 calculator an it had that massive manual with it.

Also Lugs and spending a lot of time on IRC getting and helping people on freenode (don’t go there now) was a must.

The only OS that was solid as a desktop OS back then, with good usability, was BeOS. Both MacOS and Windows had stability problems (although NT/2000 were much better, but lacked app/game compatibility), and Linux was a nightmare to update and run (lots of compiling too). So the OS of choice back then for me, was BeOS. I could do everything I needed with it too.

I got tired of compiling the kernel taking a day on my Pentium pc. So I got a pile of 486s the uni was throwing out, built a Beowulf cluster out of them and soon I was able to compile the kernel in two and half days.

Games: xbill, koules, and quake1 prerelease test(8 or 16 player multi)

Crafting XFree86 config lines to get a monitor working(no auto-detect for resolution modes)

Sharing tips, on how to solve all these issues, with others at Linux User Groups(LUGs)

Hmm my first linux distro was Suse 5.x that came on 5 CDs (i think it was 1998) … can’t say I used it much, I had weird German ISDN Internet at the time and the PPPoverWhatever (forgot the exact name) just didn’t wanna work. Making music wasn’t really feasible at the time. It mostly lay dormant. I slowly climbed the learning curve and switched to Linux full-time in the mid-2000s, when a lot more things were possible …

Relevant xkcd’s

<img alt="" src="https://beehaw.org/pictrs/image/3e675f47-fdef-4405-8740-ebbb795dfe51.webp">

<img alt="" src="https://beehaw.org/pictrs/image/f5e5d2dd-b604-4243-8d31-49eef74d8aca.webp">

<img alt="" src="https://beehaw.org/pictrs/image/bd9c0029-a71c-46e1-b68b-ebdfdab08ae3.webp">

I didn’t have a Pentium processor in my computer, the internet was young, information wasn’t as ready or available, and the mindset wasn’t that you could check everything. I don’t remember how many floppy disks it took to install Slackware, but at least one read error was definitely on the way. I had a 56k modem at home, so I had printed out the installation instructions from work. Compiling everything wasn’t a problem, because I learned to code back in 1983. When I tried to figure out the refresh rate of my screen, I was afraid I would blow it up and go blind. The feeling of freedom was when you were the one who could choose everything for the first time in your virtual life.

All I know is I wish I would’ve stuck with it when I first installed but…alas…I was lazy and too dependent on GUI

The first time I ever used Linux was in high school around 2001-2002. I don’t remember what the distro was but it had drawing issues, clearly some kind of driver issue that I couldn’t figure out, on my PC so I switched back to Windows 98SE.

Not what op asked for, but it kept away from Linux at home until 2007. I started using Linux regularly in university around 2004.

You spent a few evenings downloading a hundred or so 1.44MB floppy imges over a 56kbps modem. You then booted the installer off one of those floppies, selected what software you wanted installed and started feeding your machine the stack of floppies one by one.

Once that was complete you needed to install the Linux boot loader “LiLo” to allow you the boot it (or your other OS) at power on.

All of that would get you to the point where you had a text mode login prompt. To get anything more you needed to gather together a lot of detailed information about your hardware and start configuring software to tell it about it. For example, to get XFree86 running you needed to know

• what graphics chip you had
• how much memory it had
• which clock generator it used
• which RAMDAC was on the board
• what video timings your monitor supported
• the polarity of the sync signals for each graphics mode

This level of detail was needed with every little thing

• how many heads and cylinders do your hard drives have
• which ports and irqs did your soundcard use
• was it sound blaster compatible or some other protocol
• what speeds did your modem support
• does it need any special setup codes
• what protocol did your ISP use over the phone line
• what was the procedure to setup an tear down a network link over it

The advent of PCI and USB made things a lot better. Now things were discoverable, and software could auto-configure itself a lot of the time because there were standard ways to ask for information about what was connected.

On the topic, did AOL work on linux? They were the google of their time, i can’t imagine the FOSS world thought very highly of them

It was real real rough

Imagine gnome but instead of deciding your settings for you, they had a dialog where you had to pick the settings yourself.

I had an old laptop, and my WiFi required some kind of cutter driver that wrapped broadcom, my Intel graphics didn’t work on newer kernels. It booted in 7 seconds on a 5400rpm disk though while XP took minutes.

In the late 90s you could get CDROMs from the nerds at university with everything you need on them. If you got your sound card working and could play an mp3, you felt like a master hacker who had beat the game.

I mean, you could recreate it. Just burn some old distros on a cd and get one of tgese old white pc

Linux was exciting but time consuming and not all that useful.

I used to bike into University, spend half the night downloading disk images of SLS, spend hours more installing, and spend hours more getting the X config timings working for my monitor. But when I was finally able to use the same window manager config as the Sun workstations at school I felt like King of the World! But what was I actually doing with it? Xterm and an ancient version of GCC.

That said, I created my own basic Shell in the early days and a few little utilities. So I learned a lot. I do not think I would even have attempted many things without the technical confidence that just being a Linux user brought. There was the feeling that you could do anything even though you were hardly doing anything. And new capabilities were constantly arriving so that feeling lasted years.

I started using Slackware in the late 90s - say 1998. I used it for most of my desktop applications pretty much right away.

I don’t game much so that wasn’t an issue for me.

It was definitely harder to configure. I recompiled so many kernels and told myself the speed boost from getting exactly what I needed and nothing else was impressive. It wasn’t.

I dunno. It wasn’t as polished as it is now, and was harder to configure, but it was still very good, and once you got it configured, it kept working, unlike the more popular os of the day.

I cut my teeth with DOS and Netware, used Windows until the day 98 was released (had been using the GM for a month), and cut over to Slackware as my daily driver. Dabbled with Redhat before stabilising on Debian, which I’ve never found a need to change from for my headless boxes.

One thing I specifically remember was hand tuning my X11 config to drive my 15” Trinitron at 1024x768 @ ~68Hz.

A real pain in the ass. It was still worth it to use for the experience, especially if you had an actual reason to use it. Other than that it was just an exercise in futility most of the time…and I think that’s why we loved it. It was still kinda new. Interesting. And it didn’t spoon feed you. Was quite exhilarating.

I think it really depends what you were doing. Some of us wanted to run web servers, and it was really neat that we could easily do so using very old hardware. One thing that is hard to imagine now is that, back in the day, there were not nearly as many configuration files. It was a lot easier to see what was going on, because less was going on.

These days there’s just so much more happening on your system, but at the same time advanced web search has made it possible for us to find better documentation or forums when we need to figure out how to tweak everything.

I remember kernel panic and dependency hell. But it was also wonderful to get away from win95.

What a lot of people forget is that in the early days of Linux there was no software that targeted it. Everything you would want to run on Linux was intended to run on something else like Solaris, BSD, AT&T Sytem V, SCO, AIX or something else. As a result, Linux APIs were the most generic flavor of Unix possible. Almost every thing meant for a Unix would compile and run on it and there was rarely a dependency problem.

I still miss that.