For those veteran linux people, what was it like back in 90s? I did see and hear of Unix systems being available for use but I did not see much apart from old versions of Debian in use.
Were they prominent in education like universities? Was it mainly a hobbyist thing at the time compared to the business needs of 98, 95 and classic mac?
I ask this because I found out that some PC games I owned were apparently also on Linux even in CD format from a firm named Loki.
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.
I first used Linux in the late 90s, and it was just something that worked better on an older box. I installed Red Hat on an old 286 and the fun part was honestly getting it to work and learning about computers. Then one day I realized that I was spending all my free time working inside on this thing, but I was living on the water, in the Florida Keys, with access to boats and jet skis and pretty much anything. That had been my dream my whole life and all of a sudden I was living it. And I didn’t even have to be at work, right next door, until 10am. I was on a break from school then, and that’s actually what caused me to change my major from CS. I didn’t think it would be helpful to spend my whole life indoors!
Now I’m a physics teacher and I sometimes teach my 9th graders how to use Python for simple things like graphing. I love my life and I’m really thankful I keot computers as a hobby rather than as my profession.
I am a 90s child, so I don’t completely fit your timespan, but I remember the first PC with SuSe Linux that I built with my father from old server hardware he got from his job.
Back then his job used unix and it was pretty common in his field of work. So Linux was the natural choice for a home pc. SuSe was popular back then, I think mainly because it came on CDs and had books available.
One of the main things I remember is the hassle with network drivers, having to download them on a working pc first.
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.
Ah, the golden age. I dunno, I was running FreeBSD. It was awesome. It still is.
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! :)
It was a struggle. You went to buy some device and you had to check it was not one of those windows-only ones. Modems were particularly bad, for example.
You had to read the how-tos and figure things out. Mailing lists and newsgroups were the only places to find some help.
You had to find the shop willing to honour warranty on the parts and not on the whole system, as they had no knowledge of Linux at all. But once you found them, you were a recurring customer so they were actually happy. You might even have ended up showing them memtest86!
You would still be able to configure the kernel and be able to actually know some of those names, compilation would take several hours but it was a learning experience.
You could interact with very helpful kernel developers and get fixes to test.
You could have been the laughing stock of your circles of friends, but within you, you knew who’d have had the last laugh.
And yes, Loki games had some titles working on Linux natively, Railroad Tycoon was one. Too bad they were ahead of the times and didn’t last much.
windows-only ones. Modems
And, of course, they’d almost never actually SAY that on the box, so you had to see if you could look at what exact chip was on them and explain to a retail employee why you needed to look in the box, and that no, you certainly weren’t doing something sketchy, you just use Linux instead of wait why are you calling security…
“software” modems and soundcards. yeah.
Ah yes, the (in?)famous mWave cards come to mind here.
So shitty they not only didn’t work in Linux, they ALSO never fucking worked right in Windows, either, and got IBM sued over what utter trash they were.
compilation would take several hours but it was a learning experience.
the first time i put gentoo on a g3 imac back in 2004; it took 3 days to compile everything and the computer got so hot that it warmed up the entire room like a space heater. lol
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 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.
Did you ever dual boot Linux and windows, and also have VMware installed in both so you could boot the other one from inside whichever you had booted? Because I spent an insane amount of time screwing around with that for as excruciatingly slow as it was back then.
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.
It was kind of an upstart thing and people were trying to find ways to monetize it.
My first Linux was Red Hat on a 486 in 1998 and it was different than I was used to. I was a kid who didn’t know how to startx so I just emailed a developer using pine and they helped me figure out and choose a window manager. Nobody even got mad at this barely teenager just emailing dumb questions. I got lost with fvwm95 and afterstep. I tried every window manager, mlvwm, qvwm, IceWM, etc but ended up liking blackbox the most. I had 12MB of RAM on my first Linux system, 1MB of vram and 256 colors. We were all sarcastic in a cringe, adolescent way but everyone was friendly and helpful.
There was this fascination with monkeys in pop culture, but not real monkeys–chimps and gorillas. People would throw monkey in their username or in some random nu-metal song for some reason. There were monkeys you could download for your desktop. There was this thing by PC gamer called coconut monkey. I don’t know what that’s all about. And anyway I associate this period with the foot logo of Gnome, which was unprofessional but that was the point. Also, gimp was a funny name for an app, and pan stood fo pimp ass news.
I discovered Slashdot and Freshmeat and Sourceforge and kuro5hin. Usenet groups were great back then. So was irc. I trolled Slashdot and got negative karma and for the next 15 years before we all moved to SoylentNews, my comments started at -1.
Nobody knew how to pronounce Linux. Some people said Line-X because his name was Linus like on Charlie Brown, and some people said Leenucks.
At some point it became a corporate thing and the term Linux was everywhere. Randomly on magazine covers. There was also this divide, almost marketing driven, it seemed that people who liked warez and whatever started to love Microsoft and shit on Linux. So gamers especially started to shit talk and that’s the first time that being a computer nerd wasn’t like this unifying concept, there was an us versus them divide. People who could compile code they wrote and who were genuinely curious versus people who just wanted to download a bunch of shit and show you how big their start menu was and play games. I think this divide still exists.
There was a bunch of commercial software for Linux too. Metro-X, Accelerated X, Motif, Applixware, Star Office. Descent 3. One of the Quakes. Motif, the toolkit, looked amazing. I thought CDE with themes was the coolest looking thing ever. But I couldn’t afford CDE so I used XFce which was an XForms knockoff. And then enlightenment came along and pushed the boundaries of what we thought a desktop would be. Also, I was able to drag console windows with transparency on that 486 on e16.
Debian kind of had an elitist community and talked down to people so I never used it. I liked Slackware the most and spent a weekend downloading the floppies over a dialup connection. That led to me discovering FreeBSD in 1999, which I stuck with for almost a decade.
Later, a comp sci student, I didn’t see Linux at university in the labs. It was Solaris and macOS in the mid 2000s. Eventually, the Solaris computers were shut down and replaced with more Macs.
My girlfriend’s Windows ME computer was so full of spyware so I installed SuSE with KDE on it for her in her dorm. And she was able to do her papers in AbiWord. And 20+ years later we are married and it all worked out.
I finally switched to Debian stable about 4 years ago and have no complaints. It’s a lot easier now.
Wow, thanks for sharing all that, was well written and really allowed for a peek into what it was like!
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.
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 somebody would vome and 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 in the server-side.
I have to say, as a Linux fan in the 90’s it was very cool to see Linux eating the whole server space, replacing older Unix while Microsoft tried desperately to grow Window on the server market.
I was already a dev in a small IT consultancy by the end of the decade, and having ended up as “one of the guys you go to for web-based interfaces”, I did my bit pushing Linux as a solution, though I still had to use IIS on one or two projects (even had to use Oracle Web Application Server once), mainly because clients trusted Microsoft (basically any large software vendor, such as Microsoft, IBM or Oracle) but did not yet trust Linux.
That’s why I noticed the difference that Red Hat with their Enterprise version and Support Plans did on the acceptability of Linux.
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.
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! :)
I recently tried to compile Crossover’s Wine from source. I went through many compile errors, fixed dependency issues and started over etc. In the end I think I compiled vanilla Wine imstead of Crossover (there are different source tarballs) because O365 still refused to install lol.
Slackware and Red Hat were the two distros in use in the mid 90s.
My local city used proper UNIX, and my university had IRIX workstations and SunOS servers. We used Linux at my ISP to handle modem pools and web/mail/news servers. In the early 2000s we had Linux labs, and Linux clusters to work on.
Linux on the desktop was a bit painful. There were no modules. Kernels had to fit into main memory. So you’d roll your own kernel with just the drivers you needed. XFree86 was tricky to configure with timings for your CRT monitors. If done wrong, you could break your monitor.
I used FVWM2 and Enlightenment for many years. I miss Enlightenment.
I used Enlightenment on Arch Linux for a year, in 2020-21. The PC had 4G ram and an HDD, Enlightenment was blazing fast. I could type enlightenment_start to a tty and reach a Wayland desktop under a second with 250M ram used total. E is still alive and kicking.
I miss enlightenment
Me too! Has E17 come out yet? 😆
E16 was better
Enlightenment is on version 26
Guess you missed the joke that it was 13 years between E16 and E17 🙂
that was the last time i contributed; i created a LCARS port and now there are hundreds of them everywhere.
LCARS interface… that is something I haven’t seen in a loooooooong time
SGI workstations had the best GUI. That shit looked straight out of Hollywood
How wrong did you have to be to break your monitor? Because I’m positive I got it very wrong a whole lot of times and never managed that.
I managed to make mine do some very worrying noises, but none of my monitors broke either, even though the bandwidth I based my calculations on was often kinda made up.
By the late 90’s most monitors were smart enough to detect when sync speed was too far off and not try to display an image.
It was the old monitors that only supported a single or fixed set of scan rates that you had to worry about damaging. Some could be very picky and others were more tolerant.Thank goodness I had a newer monitor then, because I would definitely have toasted several.
If done wrong, you could break your monitor.
You mean your graphic drivers, right? not your actual hardware…
No. The wrong timing parameters could definitively break your hardware.
@andrewth09 I bricked a monitor when I tried to fiddle with the graphics settings in Linux back in the late 90s (tried to get it to run on 1280*1024 - which was considered “hi resolution” back then). I had to buy a new monitor. Then installed Windows and only returned to Linux a long time after that.
Oh yeah. I remember all the warnings plastered all over the X11 config file about how dangerous the settings were if you got them wrong.
The lessons we learn…