In the early 90s all the "cool kids" (for a techie definition of "cool", i.e. hackers) at my University (a Technical one in Portugal with all the best STEM degrees in the country) used Linux - it was actually a common thing for people to install it in the PCs of our shared computer room.

Later in that decade it was already normal for it to be used in professional environments for anything serving web pages (static or dynamic) along with Apache: Windows + IIS already had a lower fraction of that Market than Linux + Apache.

If I remember it correctly in the late 90s RedHat started providing their Enterprise Version with things like Support Contracts - so beloved by the Corporates who wanted guarantees that if their systems broke the supplier would fix them - which did a lot to boost Linux use on the backend for non-Tech but IT heavy industries.

I would say this was the start of the trend that would ultimately result in Linux dominating on the server-side.

I went to college in 93, and they ran a Unix mainframe with thin clients connected to it in the computer labs.

I didn’t really know much about any computers then, but I learned quick and had nerdy friends teach me a lot. Home computers ran DOS, but this fancy thing called Linux had entered the scene and nerds played with it.

I remember it being a bear. My comp sci roommate did most of the work, but he’d dole out mini projects to me to help him out. You had to edit text files with your exact hardware parameters or else it wouldn’t work. Like resolutions, refresh rates, IRQs, mouse shit, printer shit - it was maddening. And then you’d compile that all for hours. And it always failed. Many hardware things just weren’t ever going to work.

Eventually we got most things working and it was cool as beans. But it took weeks - seriously. We were able to act as a thin client to the mainframe and run programs right from our apartment instead of hauling ourselves to the computer lab. Interestingly, on Linux, that was the first time I had ever gotten a modem and a mouse working together. It was either/or before that.

It was both simultaneously horrific and fantastic at the same time. By the time windows 95 rolled out, the Unix mainframe seemed old and archaic. All the cool kids were playing Warcraft 2 and duke nukem 3D.

I tried slackwear in '94. Getting it running was no big deal, but I had zero experience and documentation / help guides were thin. Installing applications or getting peripherals to work was prohibitively difficult without having a pretty decent amount of knowledge about it.

My high school had a rather large dose/novell Network but there was no internet yet. BBS's were a thing and you could get a lot of installers and information from them. But they were all running in dos for the most part

My college had a VAX, it was more or less there just to get email and power a metric ass load of terminals in the library for research purposes. They really tried to keep you out of the CLI, everything was menued. I figured out that you could go for it to a South African University about seven times in a row and it would explode and give you a telnet session, but even then I wasn't really working with an OS shell. The school had a computer lab. It was all Windows 3 and Novell, No internet for the longest time.

My ISP had options to dial up into a terminal session. My home dial up line was awful. Trying to FTP over PPP was a fool's errand. I started getting used to connecting to my ISP and FTPing files down to their local node on with their T1 and then switching over to z modem to download the files to my house with the ability to auto restart on failure.

I didn't try to run a Linux based OS again until Gnome came out.

I started with Suse 5 when it came out, as something I was interested in fucking about with. I didn't have internet access at that time, but I did had a couple of books about it (the distro came with a book as well). It was a couple of CDs and a boot floppy disk (booting from CD wasn't really a thing).

I used it for years for software development and simple tasks like Word processing. Getting my printer working on the thing was a chore, as was basically anything. Especially without internet solving issues was sometimes simply impossible. My scanner simply didn't work. Getting the desktop environment to run was very hard, I struggled with it for a long time. And once I got it working properly, I got a new videocard and it broke the whole thing again.

The system was very painful to use, it was super cool, but almost nothing ever worked right. And trying to fix shit usually made it worse. But once you did get it working right, it was simply awesome. And the feeling of accomplishment was awesome after finally getting something right. For software development on the terminal it was pretty awesome though. Back then I did almost everything in text mode, as I was used to DOS before that. Going into Windows was something you did only sometimes with Windows 3.11 (and even 95) and I did the same in my Linux environment. The desktop environment used up a lot of memory and was pretty slow, so I preferred the console. It was only later booting into the desktop became the norm (around the Windows 98 era).

I used Suse till version 6.1 (still have that box). I bought version 7 (still have that box as well), but never really used it.

Back then I used Debian to create small internet routers for my friends. I got an old compact computer, put in a floppy with Debian, a couple of network cards and created small NAT boxes like that. This was before NAT routers were the norm, people just had internet on 1 machine, connected directly. But as computers became cheaper, a lot of folk had more than 1 computer in the home. With no real way to share the internet connection between the different computers. Microsoft created the Internet Connection Sharing feature, but that was pretty slow, disconnected often and ate resources on your "main" PC. So my little boxes worked great, I helped people setup a home network, connected my magic box to get every system online. Also helped them setup some port forwarding for the stuff they used.

Because I used Debian a lot, I switched over to Debian for my main rig when Suse 7 released. Used Potato, Woody, Sarge and Etch a lot. Switched around between Debian and Ubuntu in the Lenny and Squeeze era. Have been using Ubuntu ever since, never really had a reason to switch. Debian compared to Suse was so nice, I really liked the way Debian did things. It made a lot more sense for me in my head compared to Suse.

As I fucked around with computers a lot, I always had both Linux and DOS/Windows machines running and even had a couple of dual boot systems. For any kind of gaming DOS/Windows was required back then and I did love to game. I do think Windows 10 will be my last Microsoft OS, since Windows 11 absolutely sucks (use it at work, I hate it). Work stuff has become less and less of an issue to get stuff done on Linux just as well as on Windows. And gaming has come leaps and bounds due to the work on the Steamdeck.

So hope to fully ditch Microsoft in the near future, even though my first ever computer in 1984 ran Microsoft firmware with Microsoft Basic being the default user interface.

I'm not sure I consider myself a "veteran" since I still used Windows most of the time back then, but I used it in the late 90s. This is all anecdotal from my perspective, but the late 90s Linux experience was pretty rough on the desktop side, especially installing it. I actually rarely saw Debian in use, it was usually Red Hat for the sane people or Slackware for the lunatics. There were a few notable Linux game ports, but generally speaking, gaming wasn't something most people did or even expected to do in Linux. I think I had a small handful games that weren't terminal roguelikes: Doom, Quake, Tux Racer, and Alpha Centauri ( this one might have been early 2000s, hard to recall ). I can't say I personally saw anyone openly using it at the university level in almost any form when I attended, I saw a lot of Unix though. Everyone I knew that was using Linux was younger and did have a slightly hobbyist leaning, with the more serious people usually using OpenBSD or FreeBSD.

There's already a ton of great examples which I can relate (I've been using linux since 1998 or 99) but maybe the biggest difference today, apart from that everything is SO MUCH EASIER now, is that the internet wasn't really the thing it is today. Specially the bandwidth. It took hours and hours over the phone line to download anything, on a good day you could get 100MB just under 4 hours. Of course things were a lot smaller too back then, but it still took ages and I'm pretty sure I now have more bandwidth on my home connection than most of the local universities had back in the 90s.

Linux was in use on some university machines although I lot of them were still running Sun hardware OS. The main distribution I used at the time was Slackware.

You have several long and comprehensive answers so please allow me to add an emotional one:

Fucking compile error in hour six of what you estimated to be a four hour compile job because of a mistake you made that you found within 5 seconds after the error!!

Fucking why doesn't this compilation start I can't find my mistake for hours?!

Where does this module come from?! What do you mean "root kit"? Learning was fun!

It all was fun! :)

Well, XFree86 ( before Xorg and before KMS ) was an adventure. I spent hours guessing the vertical and horizontal frequencies of my monitor trying to get decent resolutions.

Other than that, Linux was way more work but “felt” powerful relative to OS options of the time. Windows was still crashy. The five of us that used OS/2 hated that it still had a lot of 16 bit under the hood. Linux was pure 32 bit.

Later in the 90’s, you could run a handful of Windows apps on Linux and they seemed to run better on Linux. For example, file system operations were dramatically faster.

And Linux was improving incredibly rapidly so it felt inevitable that it would outpace everything else.

The reality though was that it was super limited and a pain in the ass. “Normal” people would never have put up with it. It did not run anything you wanted it to ( if you had apps you liked on Mac, Windows, OS/2, Amiga, NeXTstep, BeOS, or whatever else you were using ( there were of potential options at the time ). But even for the pure UNIX and POSIX stuff, it was hard.

Obviously installation was technical and complex. And everything was a hodge-podge of independently developed software. “Usability” was not a thing. Ubuntu was not release until 2004.

Linux back then was a lot of hitting FTP sites to download software that you would build yourself from source. Stuff could be anywhere on the Internet and your connection was probably slow. And it was dependency hell so you would be building a lot of software just to be able to build the software you want. And there was a decent chance that applications would disagree about what dependencies they needed ( like versions ). Or the config files would be expected in a different location. Or the build system could not find the required libraries because they were not where the Makefile was looking for them.

Linux in the 90’s had no package management. This is maybe the biggest difference between Linux then and Linux now. When package management finally arrived, it came in two stages. First, came packages but you were still grabbing them individually from FTP. Second came the package manager which handled dependencies and retrieval.

The most popular Linux in the mid to late 90’s was Red Hat. This was before RHEL and before Fedora. There was just “Red Hat Linux”. Red Hat featured RPMs ( packages ) but you were still installing them and any required dependencies yourself at the command line. YUM ( precursor to NRF ) was not added until Fedora Core 1 was release in 2003!

APT ( apt-get ) was not added to Debian until 1998.

And all of this meant that every Linux system ( not distro — individual computer ) was a unique snowflake. No two were alike. So bundling binary software to work on “Linux” was a real horror-show. People like Loki gave it a good run but I cannot imagine the pain they went through. To make matters worse, the Linux “community” was almost entirely people that had self-selected to give up pre-packaged software and to trade sweat-equity for paying for stuff. Getting large number of people to give you money for software was hard. I mean, as far as we have come, that is still harder on Linux than on Windows or macOS.

You can download early Debian or Red Hat distros today if you want to experience it for yourself. That said, even the world of hardware has changed. You will probably not be wrestling IRQs to get sound or networking running on modern hardware or in a VM. Your BIOS will probably not be buggy. You will have VESA at least and not be stuck on VGA. But all of that was just “computing” in the 90’s and the Windows crowd had the same problems.

One 90s hardware quirk was “Windows” printers or modems though where the firmware was half implanted in Windows drivers. This was because the hardware was too limited or too dumb to work on its own and to save money your computer would do some of the work. Good luck having Linux support for those though.

Even without trying old distros, just try to go a few days on you current Linux distro without using apt, nrf, pacman, zypper, the GUI App Store, or what have you. Imagine never being able to use those tools again. What would that be like?

Finally, on my much, much slower 90’s PC, I compiled my own kernel all the time. Honestly multiple times per month I would guess. Compiling new kernels was a significant fraction of where my computing resources went at the time. I cannot remember the last time I compiled a kernel.

It was a different world.

When Linus from LTT tried Linux not that long ago ( he wanted to game ), he commented that he felt like he was playing “with” his computer instead of playing “on” his computer. That comment still describes Linux to some extent but it really, really captures Linux in the 90’s.

Heard about linux from someone at school in -95, I was 15 at the time. No idea where he had heard about it. Brought a stack of floppy disks and downloaded slackware on a school computer. Of course some of the disks had read errors so had to copy them again the next day but eventually I got slackware installed. In spring of -96 redhat 3.0.3 was released which I for some reason bought the full version of, still have the box in my bookcase. Since then I have been a pretty much 100% linux desktop user. Well 95% since I was dual booting windows for games for a long time.

I spent a lot of time back then learning linux by experimentation and hanging out on IRC talking to people about linux. As others have said, you had to compile the kernel because there were no kernel modules (had forgotten about that!) and I remember being quite fast in navigating the kernel configuration menus. I wouldn't even know where to start nowadays! :)

Loki distributed alpha centauri if I remember correctly? Awesome game. The windows version is actually easier to run on Linux than the original Linux release nowadays.

From my perspective, anything pre-ubuntu was a colossal ballache for a desktop system. I played around with suse, mandrake, etc prior to that but getting things working often felt like a chore.

I got a disk of suse Linux from a library book. I put it on my laptop and it worked-ish.

I didn't know what partitions were so I messed up my laptop pretty bad. But I learned more in that little bit than my undergrad degree.