From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
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)
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.
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.
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.
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.
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 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.
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)
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.
I started programming in DOS professionally in January 1991. It was pretty clear how bad Microsoft sucked by February of 1991, and blindingly obvious when they "updated" DOS more than annually with "95% backward compatibility" which translated to: "we just broke all your programs and you're only going to have to figure out which 5% of your code you're going to have to update to make it work in this version - aaaaand, by the time you do that we will be releasing a newer version! ;-P "
Something called DrDOS came along and we used it just because it wasn't updating and breaking backward compatibility so often. Since 640k wasn't enough for us even then, we ended up putting the kludge "Phar-Lap 32 bit extender" libraries on our product so we could access all the cheap RAM that systems were being shipped with (2MB was pretty much standard by 1992).
Then there was the day that McAffee decided that our product's main .exe was a virus. It wasn't. It wasn't infected with anything. It didn't do anything vaguely resembling malware. McAffee just had a false positive pattern match with our software.
The Microsoft treadmill was a very real thing all through the 1990s - much like Android and iOS are today. Sure, you've got a cool idea for an app, but we're going to keep shifting the OS underneath you so that you're spending 90%+ of your time just recoding your same old app for the latest OS release. That way you don't have any time to innovate and maybe threaten our business model.
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.
The days before Walnut Creak CD-ROM :-) Waiting for FIDO.NET to be synced at midnight… I think that’s what it was called… shit’s getting hazy.
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.
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.)
I remember kernel panic and dependency hell. But it was also wonderful to get away from win95.
We didn't have -R, you had to go into every subdirectory and run the command manually.
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
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 ...
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.