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.

  • @fubarx@lemmy.world
    link
    fedilink
    46 minutes ago

    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.

  • @grapemix@lemmy.ml
    link
    fedilink
    124 minutes ago

    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.

  • ☂️-
    link
    fedilink
    154 minutes ago

    it was garbage.

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

  • @madame_gaymes@programming.dev
    link
    fedilink
    English
    3
    edit-2
    41 minutes ago

    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

  • Züri
    link
    fedilink
    114 hours ago

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

  • @dkc@lemmy.world
    link
    fedilink
    English
    84 hours ago

    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.
    • @GalacticGrapefruit@lemmy.world
      link
      fedilink
      2
      edit-2
      59 minutes ago

      <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.> Are you telling me that one dev for X.org could set someone’s monitor on fire by fucking with four lines of code?

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

  • @Kongar@lemmy.dbzer0.com
    link
    fedilink
    English
    3
    edit-2
    3 hours ago

    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.

    • @GalacticGrapefruit@lemmy.world
      link
      fedilink
      156 minutes ago

      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.

  • @hobbsc@lemmy.sdf.org
    link
    fedilink
    English
    11
    edit-2
    5 hours ago

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

    and walnut creek was doing the Lord’s work.

    • @bajabound@lemmy.world
      link
      fedilink
      54 hours ago

      Walnut Creek and infomagic saved me so much headache. Can’t beat the bandwidth of a FedEx truck, especially when you’re 28.8 at home.

    • @catloaf@lemm.ee
      link
      fedilink
      English
      34 hours ago

      It was always fun saying +++ATH in IRC to see who hadn’t configured their escapes properly

  • Beej Jorgensen
    link
    fedilink
    74 hours ago

    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.

    • deadcatbounce
      link
      fedilink
      11 hour ago

      Having grown up with Acorn Atoms. BBC Micro, MS and DRDOS, Gem, Xerox something, Windows 1, don’t remember 2, 3.0 to 3.11, NT. I didn’t realise how nice early (2004) Linux was until I used it in a Windows server hosted VM to handle my phone calls (VoIP@home or something it was called).

      I did everything I could to ditch Windows after that. The webification of QuickBooks was the final release.

  • Monounity
    link
    fedilink
    23 hours 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.

  • @floo@retrolemmy.com
    link
    fedilink
    English
    61
    edit-2
    8 hours ago

    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.

    • d00phy
      link
      fedilink
      English
      4
      edit-2
      5 hours ago

      Remember when packages like RPM were first introduced, and it was like, “cool, I don’t have to compile everything!” Then you were introduced to Red Hat’s version of DLL-Hell when the RPM couldn’t find some obsure library! Before YUM, rpmfind.net was sooo useful!

      • @catloaf@lemm.ee
        link
        fedilink
        English
        24 hours ago

        I still use pkgs.org pretty frequently when I need to find versions of packages and their dependencies across different distros and versions of distros. I had to use that to sneakernet something to fix a system just this past week.

      • @floo@retrolemmy.com
        link
        fedilink
        English
        1
        edit-2
        4 hours ago

        Shit like that was the last straw for me and I ended up bailing on Linux for, like, 10 years until I got back into it around 2006.

    • TFO Winder
      link
      fedilink
      198 hours ago

      Remember the slow internet jad to wait overnight for 40 megabyte game and finally finding out it didn’t work.

  • @callmemagnus@lemmy.world
    link
    fedilink
    86 hours ago

    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.