We didn't have -R, you had to go into every subdirectory and run the command manually.
Linux
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
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
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.
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.
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.
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.
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.
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.
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.
Imagine a pile of floppy disks, with stuffs inscribed on it that you never heard of....
... will you insert one into your computer and reboot it?
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.
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.
Had to google, here's wikipedia links for those not in the know!
They were great, probably put most of their profits into running a very fast FTP site.
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.)
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.
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.
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.
I loved reading HOWTOs, they were a bit like scene zines, but the content wasn't that helpful indeed
There was a similar question a while ago with some nice reads in the answers :)
LUGs were very important back then especially when you were new.
First time I format the whole disk, all msdos data (games) lost. I managed to install it then I opened vim to edit a file and I couldn't get out of vim I know it's a cliche, but there is real. To get out I have to call a friend, using the landline, the one who lends me the floppy disks (or maybe it was magazine cd) and ask he how to get out, he says, just press Shift and Z twice.