this post was submitted on 19 Apr 2025
196 points (97.6% liked)

Linux

54035 readers
1448 users here now

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.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
 

I really wish that I was born early so I've could witness the early years of Linux. What was it like being there when a kernel was released that would power multiple OSes and, best of all, for free?

I want know about everything: software, hardware, games, early community, etc.

(page 2) 50 comments
sorted by: hot top controversial new old
[–] [email protected] 15 points 2 weeks ago

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.

[–] [email protected] 10 points 2 weeks ago (1 children)

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.

load more comments (1 replies)
[–] [email protected] 4 points 2 weeks ago* (last edited 2 weeks ago)

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.

[–] [email protected] 24 points 2 weeks ago (3 children)

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.

[–] [email protected] 6 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Lol! 'Member Afterstep?

The desktop stretched across 4 screens was enough to hook me for life.

Xeyes.. so many terminals.. the artwork was artwork.. wtf is transparency?! 😁 It was an amazing time to be a geek.

load more comments (1 replies)
load more comments (2 replies)
[–] [email protected] 27 points 2 weeks ago (1 children)

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.

[–] [email protected] 4 points 2 weeks ago

That's great bit of history

It may be useful for people reading if you could add headers about when each decade starts, since you have many of them there

[–] [email protected] 2 points 2 weeks ago (1 children)

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.

[–] [email protected] 3 points 2 weeks ago (1 children)

How many times did I read the condescending "HOW-TO sound drivers" with it's condescending opening of "If you must hear biff bark" and it's virtually always unhelpful content. Maybe one install in 10 would benefit from the pearls of Linux Audio wisdom contained therein, and it was the best available source for YEARS.

[–] [email protected] 2 points 2 weeks ago

I loved reading HOWTOs, they were a bit like scene zines, but the content wasn't that helpful indeed

[–] [email protected] 10 points 2 weeks ago (3 children)

it was garbage.

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

[–] [email protected] 9 points 2 weeks ago

I tried to use Slackware in the mid 90s. After two solid days trying to get my ppp dialup connection to come up after a reboot - it would come up in the first boot after install, run for days like that, but after any reboot it was dead and gone and nobody on the internet seemed to know how to deal with it. "Real men" didn't use dialup, and people on dialup (self included) had no clue.

I declared it "not ready for prime time" due to that, and issues with sound drivers, and ignored it until 2003. In 2003 I tried some Cygwin and was impressed with its performance, so very close to "bare metal" Ubuntu. In 2004-5 the 64 bit AMD chips were coming out and I used Gentoo to build a true 64 bit system addressing 8GB of RAM - there wasn't really any other option.

I got tired of compiling every little part of the system from source for days on end and migrated to various flavors of Ubuntu / Debian, which by 2006-7 was becoming a viable desktop alternative. Before that you ALWAYS had to have a Windows machine for something, usually several somethings. At this point I only use my company issued Windows laptop when I need to connect to the company VPN, which can be months between needs depending on what I'm doing. My wife and I use Ubuntu full time now.

load more comments (2 replies)
[–] [email protected] 8 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

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)

BSD Daemon

[–] [email protected] 4 points 2 weeks ago

Gentoo got pretty well defined / easy to compile by 2004 - I managed to get a 64 bit system built and working after a couple of tries, each try taking multiple days of course.

[–] [email protected] 2 points 2 weeks ago

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

[–] [email protected] 5 points 2 weeks ago

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

[–] [email protected] 6 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

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.

[–] [email protected] 2 points 2 weeks ago (1 children)

win8 made us realize

Bruh you were late. Vista sucked, 7 sucked, they were shit since XP. Sure, I kept using it until 10 because I was afraid linux still didn't work, but XP was the last time I was happy with computers until I installed Fedora.

load more comments (1 replies)
[–] [email protected] 5 points 2 weeks ago

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.

[–] [email protected] 4 points 2 weeks ago (1 children)

Yeah, I jumped ship right around the time Win8 came out. 14.04 was an interesting time to start learning. I was obsessed with trimming out bloat, so I used a tool to uninstall orphaned packages. Problem was, it also deleted some dependencies for GNOME.

I had, to quote the most helpful and humorous person in an Ubuntu forum post, "borked it so bad it had to be nuked from orbit."

I have since learned my lesson and learned to be a little bit more careful with the magical responsibilities of sudo.

[–] [email protected] 2 points 2 weeks ago

I have turned to scripting all of my desktop mods and keeping them in a git repo. So, when I nuke a system from orbit all I have to do is install fresh, add git, check out my repo and run the scripts.

[–] [email protected] 4 points 2 weeks ago

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.

[–] [email protected] 3 points 2 weeks ago

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.

[–] [email protected] 16 points 2 weeks ago (1 children)

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

[–] [email protected] 3 points 2 weeks ago

Yeah those manuals were great i still have mine.

[–] [email protected] 17 points 2 weeks ago (2 children)

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.
[–] [email protected] 3 points 2 weeks ago

I don’t recall doing any regular updates

You needed to buy a modem to get online

If you stay offline, you don't need upgrading to prevent virus or hacking. That's the norm in the good old days.

[–] [email protected] 5 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Jesus Christ, thanks for that, I didn't need to sleep tonight.

[–] [email protected] 6 points 2 weeks ago

Monitors don't work like that anymore. The ones that could catch on fire are pretty much all in the landfills by now.

load more comments
view more: ‹ prev next ›